12266 lines
696 KiB
HTML
12266 lines
696 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="UTF-8">
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
<title>Vendor Punchlist Report</title>
|
||
<style>
|
||
* {
|
||
margin: 0;
|
||
padding: 0;
|
||
box-sizing: border-box;
|
||
}
|
||
|
||
body {
|
||
font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, 'Helvetica Neue', Arial, sans-serif;
|
||
line-height: 1.6;
|
||
color: #1f2937;
|
||
background-color: #f9fafb;
|
||
padding: 20px;
|
||
}
|
||
|
||
.container {
|
||
max-width: 1600px;
|
||
margin: 0 auto;
|
||
background: white;
|
||
border-radius: 8px;
|
||
box-shadow: 0 4px 6px rgba(0,0,0,0.1);
|
||
padding: 40px;
|
||
}
|
||
|
||
header {
|
||
border-bottom: 3px solid #2563eb;
|
||
padding-bottom: 25px;
|
||
margin-bottom: 30px;
|
||
}
|
||
|
||
h1 {
|
||
color: #1e40af;
|
||
font-size: 2.5em;
|
||
margin-bottom: 10px;
|
||
font-weight: 600;
|
||
}
|
||
|
||
.meta {
|
||
color: #6b7280;
|
||
font-size: 0.95em;
|
||
}
|
||
|
||
.filters-bar {
|
||
background: #f3f4f6;
|
||
padding: 20px;
|
||
border-radius: 8px;
|
||
margin-bottom: 30px;
|
||
border: 1px solid #e5e7eb;
|
||
}
|
||
|
||
.filters-title {
|
||
font-weight: 600;
|
||
color: #374151;
|
||
margin-bottom: 15px;
|
||
font-size: 1.1em;
|
||
}
|
||
|
||
.filters-grid {
|
||
display: grid;
|
||
grid-template-columns: repeat(auto-fit, minmax(200px, 1fr));
|
||
gap: 15px;
|
||
margin-bottom: 15px;
|
||
}
|
||
|
||
.filter-group {
|
||
display: flex;
|
||
flex-direction: column;
|
||
}
|
||
|
||
.filter-label {
|
||
font-size: 0.85em;
|
||
color: #6b7280;
|
||
margin-bottom: 5px;
|
||
font-weight: 500;
|
||
}
|
||
|
||
.filter-input {
|
||
padding: 8px 12px;
|
||
border: 1px solid #d1d5db;
|
||
border-radius: 6px;
|
||
font-size: 0.95em;
|
||
background: white;
|
||
color: #1f2937;
|
||
}
|
||
|
||
.filter-input:focus {
|
||
outline: none;
|
||
border-color: #2563eb;
|
||
box-shadow: 0 0 0 3px rgba(37, 99, 235, 0.1);
|
||
}
|
||
|
||
.filter-select {
|
||
padding: 8px 12px;
|
||
border: 1px solid #d1d5db;
|
||
border-radius: 6px;
|
||
font-size: 0.95em;
|
||
background: white;
|
||
color: #1f2937;
|
||
cursor: pointer;
|
||
}
|
||
|
||
.filter-select:focus {
|
||
outline: none;
|
||
border-color: #2563eb;
|
||
box-shadow: 0 0 0 3px rgba(37, 99, 235, 0.1);
|
||
}
|
||
|
||
.filter-actions {
|
||
display: flex;
|
||
gap: 10px;
|
||
margin-top: 10px;
|
||
}
|
||
|
||
.btn {
|
||
padding: 8px 16px;
|
||
border: none;
|
||
border-radius: 6px;
|
||
font-size: 0.9em;
|
||
font-weight: 500;
|
||
cursor: pointer;
|
||
transition: all 0.2s;
|
||
}
|
||
|
||
.btn-primary {
|
||
background: #2563eb;
|
||
color: white;
|
||
}
|
||
|
||
.btn-primary:hover {
|
||
background: #1d4ed8;
|
||
}
|
||
|
||
.btn-secondary {
|
||
background: #6b7280;
|
||
color: white;
|
||
}
|
||
|
||
.btn-secondary:hover {
|
||
background: #4b5563;
|
||
}
|
||
|
||
.results-count {
|
||
color: #6b7280;
|
||
font-size: 0.9em;
|
||
margin-top: 10px;
|
||
}
|
||
|
||
.quick-filters-bar {
|
||
background: #f9fafb;
|
||
padding: 20px;
|
||
border-radius: 8px;
|
||
margin-bottom: 30px;
|
||
border: 1px solid #e5e7eb;
|
||
}
|
||
|
||
.quick-filters-title {
|
||
font-weight: 600;
|
||
color: #374151;
|
||
margin-bottom: 15px;
|
||
font-size: 1.05em;
|
||
}
|
||
|
||
.quick-filters {
|
||
display: flex;
|
||
gap: 12px;
|
||
flex-wrap: wrap;
|
||
}
|
||
|
||
.quick-filter-btn {
|
||
padding: 10px 20px;
|
||
border: 2px solid #2563eb;
|
||
border-radius: 6px;
|
||
font-size: 0.95em;
|
||
font-weight: 500;
|
||
cursor: pointer;
|
||
transition: all 0.2s;
|
||
background: white;
|
||
color: #2563eb;
|
||
}
|
||
|
||
.quick-filter-btn:hover {
|
||
background: #eff6ff;
|
||
border-color: #1d4ed8;
|
||
}
|
||
|
||
.quick-filter-btn.active {
|
||
background: #2563eb;
|
||
color: white;
|
||
border-color: #2563eb;
|
||
}
|
||
|
||
.summary-cards {
|
||
display: grid;
|
||
grid-template-columns: repeat(auto-fit, minmax(180px, 1fr));
|
||
gap: 20px;
|
||
margin-bottom: 40px;
|
||
}
|
||
|
||
.summary-card {
|
||
background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);
|
||
color: white;
|
||
padding: 24px;
|
||
border-radius: 8px;
|
||
text-align: center;
|
||
box-shadow: 0 2px 4px rgba(0,0,0,0.1);
|
||
}
|
||
|
||
.summary-card h3 {
|
||
font-size: 2.2em;
|
||
margin-bottom: 8px;
|
||
font-weight: 600;
|
||
}
|
||
|
||
.summary-card p {
|
||
opacity: 0.95;
|
||
font-size: 0.95em;
|
||
font-weight: 500;
|
||
}
|
||
|
||
.summary-card.success {
|
||
background: linear-gradient(135deg, #10b981 0%, #059669 100%);
|
||
}
|
||
|
||
.summary-card.warning {
|
||
background: linear-gradient(135deg, #f59e0b 0%, #d97706 100%);
|
||
}
|
||
|
||
.summary-card.danger {
|
||
background: linear-gradient(135deg, #ef4444 0%, #dc2626 100%);
|
||
}
|
||
|
||
.vendor-section {
|
||
margin-bottom: 40px;
|
||
border: 1px solid #e5e7eb;
|
||
border-radius: 8px;
|
||
overflow: hidden;
|
||
transition: opacity 0.3s;
|
||
}
|
||
|
||
.vendor-section.hidden {
|
||
display: none;
|
||
}
|
||
|
||
.vendor-header {
|
||
background: #f9fafb;
|
||
padding: 24px;
|
||
border-bottom: 2px solid #e5e7eb;
|
||
display: flex;
|
||
justify-content: space-between;
|
||
align-items: center;
|
||
flex-wrap: wrap;
|
||
gap: 20px;
|
||
}
|
||
|
||
.vendor-name {
|
||
font-size: 1.6em;
|
||
font-weight: 600;
|
||
color: #1e40af;
|
||
}
|
||
|
||
.vendor-stats {
|
||
display: flex;
|
||
gap: 20px;
|
||
flex-wrap: wrap;
|
||
}
|
||
|
||
.stat-item {
|
||
text-align: center;
|
||
padding: 12px 18px;
|
||
background: white;
|
||
border-radius: 6px;
|
||
border: 1px solid #e5e7eb;
|
||
min-width: 80px;
|
||
}
|
||
|
||
.stat-value {
|
||
font-size: 1.8em;
|
||
font-weight: 600;
|
||
color: #1e40af;
|
||
}
|
||
|
||
.stat-label {
|
||
font-size: 0.85em;
|
||
color: #6b7280;
|
||
margin-top: 5px;
|
||
font-weight: 500;
|
||
}
|
||
|
||
.vendor-content {
|
||
padding: 24px;
|
||
}
|
||
|
||
.section {
|
||
margin-bottom: 30px;
|
||
}
|
||
|
||
.section-title {
|
||
font-size: 1.25em;
|
||
font-weight: 600;
|
||
color: #374151;
|
||
margin-bottom: 15px;
|
||
padding-bottom: 10px;
|
||
border-bottom: 2px solid #e5e7eb;
|
||
}
|
||
|
||
.updates-grid {
|
||
display: grid;
|
||
grid-template-columns: repeat(auto-fit, minmax(320px, 1fr));
|
||
gap: 20px;
|
||
margin-bottom: 20px;
|
||
}
|
||
|
||
.update-box {
|
||
border: 1px solid #e5e7eb;
|
||
border-radius: 6px;
|
||
padding: 20px;
|
||
background: #f9fafb;
|
||
}
|
||
|
||
.update-box h4 {
|
||
color: #1e40af;
|
||
margin-bottom: 12px;
|
||
font-size: 1.05em;
|
||
font-weight: 600;
|
||
}
|
||
|
||
.item-list {
|
||
list-style: none;
|
||
}
|
||
|
||
.item-list li {
|
||
padding: 14px;
|
||
margin-bottom: 12px;
|
||
background: white;
|
||
border-left: 4px solid #2563eb;
|
||
border-radius: 4px;
|
||
box-shadow: 0 1px 3px rgba(0,0,0,0.08);
|
||
transition: box-shadow 0.2s;
|
||
}
|
||
|
||
.item-list li:hover {
|
||
box-shadow: 0 2px 6px rgba(0,0,0,0.12);
|
||
}
|
||
|
||
.item-list li.empty {
|
||
color: #9ca3af;
|
||
font-style: italic;
|
||
border-left-color: #d1d5db;
|
||
background: #f9fafb;
|
||
}
|
||
|
||
.item-header {
|
||
display: flex;
|
||
justify-content: space-between;
|
||
align-items: flex-start;
|
||
margin-bottom: 10px;
|
||
flex-wrap: wrap;
|
||
gap: 12px;
|
||
}
|
||
|
||
.item-name {
|
||
font-weight: 600;
|
||
color: #1e40af;
|
||
flex: 1;
|
||
font-size: 1.05em;
|
||
}
|
||
|
||
.badges {
|
||
display: flex;
|
||
gap: 8px;
|
||
flex-wrap: wrap;
|
||
}
|
||
|
||
.badge {
|
||
padding: 5px 12px;
|
||
border-radius: 4px;
|
||
font-size: 0.75em;
|
||
font-weight: 600;
|
||
text-transform: uppercase;
|
||
letter-spacing: 0.5px;
|
||
}
|
||
|
||
.badge-success {
|
||
background: #d1fae5;
|
||
color: #065f46;
|
||
}
|
||
|
||
.badge-warning {
|
||
background: #fef3c7;
|
||
color: #92400e;
|
||
}
|
||
|
||
.badge-danger {
|
||
background: #dc2626;
|
||
color: white;
|
||
}
|
||
|
||
.badge-secondary {
|
||
background: #e5e7eb;
|
||
color: #374151;
|
||
}
|
||
|
||
.badge-critical {
|
||
background: #fee2e2;
|
||
color: #991b1b;
|
||
font-weight: 700;
|
||
}
|
||
|
||
.badge-high {
|
||
background: #fed7aa;
|
||
color: #9a3412;
|
||
}
|
||
|
||
.badge-medium {
|
||
background: #fef3c7;
|
||
color: #92400e;
|
||
}
|
||
|
||
.badge-low {
|
||
background: #dbeafe;
|
||
color: #1e40af;
|
||
}
|
||
|
||
.item-details {
|
||
margin-top: 10px;
|
||
font-size: 0.9em;
|
||
color: #6b7280;
|
||
}
|
||
|
||
.item-details p {
|
||
margin-bottom: 6px;
|
||
line-height: 1.5;
|
||
}
|
||
|
||
.item-details strong {
|
||
color: #374151;
|
||
font-weight: 600;
|
||
}
|
||
|
||
.item-description {
|
||
margin-top: 8px;
|
||
color: #4b5563;
|
||
line-height: 1.6;
|
||
}
|
||
|
||
.age-days {
|
||
color: #dc2626;
|
||
font-weight: 600;
|
||
font-size: 0.9em;
|
||
}
|
||
|
||
.tabs-container {
|
||
margin-bottom: 30px;
|
||
border-bottom: 2px solid #e5e7eb;
|
||
}
|
||
|
||
.tabs {
|
||
display: flex;
|
||
gap: 0;
|
||
flex-wrap: wrap;
|
||
margin-bottom: 0;
|
||
}
|
||
|
||
.tab {
|
||
padding: 12px 24px;
|
||
background: #f3f4f6;
|
||
border: none;
|
||
border-bottom: 3px solid transparent;
|
||
cursor: pointer;
|
||
font-size: 0.95em;
|
||
font-weight: 500;
|
||
color: #6b7280;
|
||
transition: all 0.2s;
|
||
white-space: nowrap;
|
||
}
|
||
|
||
.tab:hover {
|
||
background: #e5e7eb;
|
||
color: #374151;
|
||
}
|
||
|
||
.tab.active {
|
||
background: white;
|
||
color: #1e40af;
|
||
border-bottom-color: #2563eb;
|
||
font-weight: 600;
|
||
}
|
||
|
||
.tab-content {
|
||
display: none;
|
||
}
|
||
|
||
.tab-content.active {
|
||
display: block;
|
||
}
|
||
|
||
.status-tabs {
|
||
display: flex;
|
||
gap: 0;
|
||
margin-bottom: 20px;
|
||
border-bottom: 2px solid #e5e7eb;
|
||
}
|
||
|
||
.status-tab {
|
||
padding: 10px 20px;
|
||
background: transparent;
|
||
border: none;
|
||
border-bottom: 3px solid transparent;
|
||
cursor: pointer;
|
||
font-size: 0.9em;
|
||
font-weight: 500;
|
||
color: #6b7280;
|
||
transition: all 0.2s;
|
||
}
|
||
|
||
.status-tab:hover {
|
||
color: #374151;
|
||
background: #f9fafb;
|
||
}
|
||
|
||
.status-tab.active {
|
||
color: #1e40af;
|
||
border-bottom-color: #2563eb;
|
||
font-weight: 600;
|
||
}
|
||
|
||
.status-tab-content {
|
||
display: none;
|
||
}
|
||
|
||
.status-tab-content.active {
|
||
display: block;
|
||
}
|
||
|
||
.updates-sub-tabs {
|
||
display: flex;
|
||
gap: 0;
|
||
margin-bottom: 20px;
|
||
border-bottom: 2px solid #e5e7eb;
|
||
}
|
||
|
||
.update-tab-content {
|
||
display: none;
|
||
}
|
||
|
||
.update-tab-content.active {
|
||
display: block;
|
||
}
|
||
|
||
.footer {
|
||
margin-top: 50px;
|
||
padding-top: 25px;
|
||
border-top: 2px solid #e5e7eb;
|
||
text-align: center;
|
||
color: #6b7280;
|
||
font-size: 0.9em;
|
||
}
|
||
|
||
@media print {
|
||
body {
|
||
background: white;
|
||
padding: 0;
|
||
}
|
||
|
||
.container {
|
||
box-shadow: none;
|
||
}
|
||
|
||
.filters-bar {
|
||
display: none;
|
||
}
|
||
|
||
.vendor-section {
|
||
page-break-inside: avoid;
|
||
}
|
||
}
|
||
</style>
|
||
</head>
|
||
<body>
|
||
<div class="container">
|
||
<header>
|
||
<h1>Vendor Punchlist Report</h1>
|
||
<div class="meta">
|
||
Generated: 2025-11-13 19:35:04 |
|
||
Total Vendors: 18 |
|
||
Total Items: 233
|
||
</div>
|
||
</header>
|
||
|
||
<div class="filters-bar">
|
||
<div class="filters-title">Filters & Search</div>
|
||
<div class="filters-grid">
|
||
<div class="filter-group">
|
||
<label class="filter-label">Search Items</label>
|
||
<input type="text" id="search-input" class="filter-input" placeholder="Search by name or description...">
|
||
</div>
|
||
<div class="filter-group">
|
||
<label class="filter-label">Vendor</label>
|
||
<select id="vendor-filter" class="filter-select">
|
||
<option value="">All Vendors</option>
|
||
<option value="AMZ">AMZ</option><option value="Amazon">Amazon</option><option value="Autstand">Autstand</option><option value="Autstand/Beumer">Autstand/Beumer</option><option value="Autstand/DCS">Autstand/DCS</option><option value="Beumer">Beumer</option><option value="Beumer/Datalogic">Beumer/Datalogic</option><option value="Caljan">Caljan</option><option value="DCS">DCS</option><option value="DCS/Autstand">DCS/Autstand</option><option value="DCS/Flow-Turn">DCS/Flow-Turn</option><option value="DCS/RME">DCS/RME</option><option value="Datalogic">Datalogic</option><option value="FMH/Gorbel">FMH/Gorbel</option><option value="Gorbel">Gorbel</option><option value="MFO (Amazon)">MFO (Amazon)</option><option value="MISC">MISC</option><option value="Startup (Amazon)">Startup (Amazon)</option>
|
||
</select>
|
||
</div>
|
||
<div class="filter-group">
|
||
<label class="filter-label">Status</label>
|
||
<select id="status-filter" class="filter-select">
|
||
<option value="">All Statuses</option>
|
||
<option value="Complete">Complete</option>
|
||
<option value="Monitor">Monitor</option>
|
||
<option value="Incomplete">Incomplete</option>
|
||
</select>
|
||
</div>
|
||
<div class="filter-group">
|
||
<label class="filter-label">Priority</label>
|
||
<select id="priority-filter" class="filter-select">
|
||
<option value="">All Priorities</option>
|
||
<option value="critical">Critical</option>
|
||
<option value="high">High</option>
|
||
<option value="medium">Medium</option>
|
||
<option value="low">Low</option>
|
||
</select>
|
||
</div>
|
||
</div>
|
||
<div class="filter-actions">
|
||
<button class="btn btn-primary" onclick="applyFilters()">Apply Filters</button>
|
||
<button class="btn btn-secondary" onclick="clearFilters()">Clear All</button>
|
||
</div>
|
||
<div class="results-count" id="results-count"></div>
|
||
</div>
|
||
|
||
<div class="quick-filters-bar">
|
||
<div class="quick-filters-title">Quick Filters</div>
|
||
<div class="quick-filters">
|
||
<button class="quick-filter-btn" onclick="showOnly24hUpdates()" id="filter-24h-updates">Show Only Vendors with Yesterday's Updates</button>
|
||
<button class="quick-filter-btn" onclick="showOnlyOldestUnaddressed()" id="filter-oldest-unaddressed">Show Only Vendors with Oldest Unaddressed</button>
|
||
<button class="quick-filter-btn" onclick="showAllVendors()" id="filter-all-vendors">Show All Vendors</button>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="summary-cards">
|
||
<div class="summary-card">
|
||
<h3>18</h3>
|
||
<p>Vendors</p>
|
||
</div>
|
||
<div class="summary-card">
|
||
<h3>233</h3>
|
||
<p>Total Items</p>
|
||
</div>
|
||
<div class="summary-card success">
|
||
<h3>129</h3>
|
||
<p>Closed</p>
|
||
</div>
|
||
<div class="summary-card warning">
|
||
<h3>19</h3>
|
||
<p>Monitor</p>
|
||
</div>
|
||
<div class="summary-card warning">
|
||
<h3>85</h3>
|
||
<p>Incomplete</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="tabs-container">
|
||
<div class="tabs" id="vendor-tabs">
|
||
<button class="tab active" onclick="switchVendorTab('all')" data-vendor="all">All Vendors</button>
|
||
<button class="tab" onclick="switchVendorTab('AMZ')" data-vendor="AMZ">AMZ</button><button class="tab" onclick="switchVendorTab('Amazon')" data-vendor="Amazon">Amazon</button><button class="tab" onclick="switchVendorTab('Autstand')" data-vendor="Autstand">Autstand</button><button class="tab" onclick="switchVendorTab('Autstand/Beumer')" data-vendor="Autstand/Beumer">Autstand/Beumer</button><button class="tab" onclick="switchVendorTab('Autstand/DCS')" data-vendor="Autstand/DCS">Autstand/DCS</button><button class="tab" onclick="switchVendorTab('Beumer')" data-vendor="Beumer">Beumer</button><button class="tab" onclick="switchVendorTab('Beumer/Datalogic')" data-vendor="Beumer/Datalogic">Beumer/Datalogic</button><button class="tab" onclick="switchVendorTab('Caljan')" data-vendor="Caljan">Caljan</button><button class="tab" onclick="switchVendorTab('DCS')" data-vendor="DCS">DCS</button><button class="tab" onclick="switchVendorTab('DCS/Autstand')" data-vendor="DCS/Autstand">DCS/Autstand</button><button class="tab" onclick="switchVendorTab('DCS/Flow-Turn')" data-vendor="DCS/Flow-Turn">DCS/Flow-Turn</button><button class="tab" onclick="switchVendorTab('DCS/RME')" data-vendor="DCS/RME">DCS/RME</button><button class="tab" onclick="switchVendorTab('Datalogic')" data-vendor="Datalogic">Datalogic</button><button class="tab" onclick="switchVendorTab('FMH/Gorbel')" data-vendor="FMH/Gorbel">FMH/Gorbel</button><button class="tab" onclick="switchVendorTab('Gorbel')" data-vendor="Gorbel">Gorbel</button><button class="tab" onclick="switchVendorTab('MFO (Amazon)')" data-vendor="MFO (Amazon)">MFO (Amazon)</button><button class="tab" onclick="switchVendorTab('MISC')" data-vendor="MISC">MISC</button><button class="tab" onclick="switchVendorTab('Startup (Amazon)')" data-vendor="Startup (Amazon)">Startup (Amazon)</button>
|
||
</div>
|
||
</div>
|
||
|
||
<div id="vendor-sections">
|
||
|
||
<div class="vendor-section" data-vendor="AMZ">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">AMZ</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">1</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">1</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'AMZ')" data-status="all">All (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'AMZ')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'AMZ')" data-status="oldest_unaddressed">Oldest Unaddressed (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'AMZ')" data-status="closed">Closed (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'AMZ')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'AMZ')" data-status="incomplete">Incomplete (0)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="AMZ">
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Tippers cycle continuously - rising to 100% then descending and repeating.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Tippers cycle continuously - rising to 100% then descending and repeating.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-03</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-05</p>
|
||
<p><strong>Status Updates:</strong> 11/5 - RME (@denrbin) confirmed completion
|
||
11/4 - Logic has been corrected on all but 4 Tippers. Shuttles will have 3 stage cycle (50/75/100%) and carts will have 1 cycle to 100% .Remaining 4 will be completed by 11/5
|
||
11/3 Will Johnson will deep dive correct Tipper logic is installed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="AMZ">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="AMZ">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No unaddressed items</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="AMZ">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Tippers cycle continuously - rising to 100% then descending and repeating.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Tippers cycle continuously - rising to 100% then descending and repeating.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-03</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-05</p>
|
||
<p><strong>Status Updates:</strong> 11/5 - RME (@denrbin) confirmed completion
|
||
11/4 - Logic has been corrected on all but 4 Tippers. Shuttles will have 3 stage cycle (50/75/100%) and carts will have 1 cycle to 100% .Remaining 4 will be completed by 11/5
|
||
11/3 Will Johnson will deep dive correct Tipper logic is installed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="AMZ">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="AMZ">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No incomplete items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="Amazon">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">Amazon</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">6</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">1</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">5</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'Amazon')" data-status="all">All (6)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Amazon')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Amazon')" data-status="oldest_unaddressed">Oldest Unaddressed (3)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Amazon')" data-status="closed">Closed (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Amazon')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Amazon')" data-status="incomplete">Incomplete (5)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="Amazon">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Critical Priority (3 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">A majority of the load balancing defects are being incorrectly attributed to disabled chutes when they're actually caused by "disabled" bypass belts. The team expected this metric to improve once all four virtual sorters became active, but the issue persists. Ops Engineering is now conducting a deep dive, pulling packages for container research to verify correct routing paths through the sorter. They need to confirm with Beumer that defect coding is properly registered in the system, and MFO will be contacted to rule out any mapping concerns that might be contributing to the misattribution.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> A majority of the load balancing defects are being incorrectly attributed to disabled chutes when they're actually caused by "disabled" bypass belts. The team expected this metric to improve once all four virtual sorters became active, but the issue persists. Ops Engineering is now conducting a deep dive, pulling packages for container research to verify correct routing paths through the sorter. They need to confirm with Beumer that defect coding is properly registered in the system, and MFO will be contacted to rule out any mapping concerns that might be contributing to the misattribution.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-03</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-07</p>
|
||
<p><strong>Status Updates:</strong> 11/6 Monitoring changes pending completion
|
||
11/5 due to the SEV2 on NIT sort 11/4, site would like to monitor for one more day.
|
||
11/4 Site wanted to monitor overnight to validate, if there are not any issues will be closed out 11/5.
|
||
11/3 Sorter Logic (Round Robin, Waterfall. etc.) is assigning packages to the bypass. Logic change should be implemented by 11/5.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">AWCS Multiple Destinations</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> AWCS was not sending multiple destinations for NC and Crossbelt in S02 Message</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/15 - Jamari Randle changed NC Config to have two destinations, still waiting for a change to Crossbelt Config</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The site is requesting a detailed schedule for vendor coverage to ensure 24/7 support availability.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The site is requesting a detailed schedule for vendor coverage to ensure 24/7 support availability.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-03</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Eli will provide once avail and final PO cut
|
||
11/6 POs issued for extended coverage through year-end. Updated escalation list needs redistribution to army and operations teams. OE schedule shared with OPS.
|
||
11/5 Angela, Eli, Anthony were not on the call for an update - will followup off line for expectation of coverage schedule.
|
||
11/3 PO's submitted for the Vendors to support through 12/21. Working on the schedule for OE.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (2 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Several jam points are inaccessible to RME/Ops for safety reasons, requiring vendor (DCS) callouts which significantly increases jam clear times. Long-term solutions include platforms post-peak, but for immediate peak support, WHS-approved ladders are being deployed on the mezzanine. Start Up team completed a site walkthrough on 10/28-10/29 with RME and safety. MTN6 RME will mark locations for Cotterman ladder deployment, with ladders being disassembled at ground level and reassembled on the mezzanine to cover 70-80% of elevated conveyance. Some areas will remain inaccessible due to space constraints. The site has two manual one-person lifts with six more on order for mezzanine deployment, with training scheduled next week. Operations is partnering with OE and RME to identify the top 10 jam locations and frequencies to develop a deployment strategy, while assessing whether additional vendor support is needed during the volume ramp.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Several jam points are inaccessible to RME/Ops for safety reasons, requiring vendor (DCS) callouts which significantly increases jam clear times. Long-term solutions include platforms post-peak, but for immediate peak support, WHS-approved ladders are being deployed on the mezzanine. Start Up team completed a site walkthrough on 10/28-10/29 with RME and safety. MTN6 RME will mark locations for Cotterman ladder deployment, with ladders being disassembled at ground level and reassembled on the mezzanine to cover 70-80% of elevated conveyance. Some areas will remain inaccessible due to space constraints. The site has two manual one-person lifts with six more on order for mezzanine deployment, with training scheduled next week. Operations is partnering with OE and RME to identify the top 10 jam locations and frequencies to develop a deployment strategy, while assessing whether additional vendor support is needed during the volume ramp.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-20</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 -
|
||
11/6 22-23 Cotterman ladders deployed (target was 25). Need to order more 12-step units. Two single-man lifts on order through Adam Gray. Additional lifts needed for center area and back platform.
|
||
11/5 16/25 ladders completed.
|
||
11/4 8/25 ladders have been setup on the Mezz.
|
||
11/3 25 Ladders are needed for Jam clearing on the Mezz. Currently all Ladders are assembled and must be broken down and brought up to the Mezz. Est. of 10 days completion.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Deep dive metrics analysis has revealed that between 40,000 to 50,000 defects are diverting to PS daily. Using Grafana Lane watch, the data shows that Jackpot chutes (11001, 12098, 13003, 14086) are receiving 30% to 50% of the site's daily processed volume, indicating a significant diversion issue that needs investigation.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Deep dive metrics analysis has revealed that between 40,000 to 50,000 defects are diverting to PS daily. Using Grafana Lane watch, the data shows that Jackpot chutes (11001, 12098, 13003, 14086) are receiving 30% to 50% of the site's daily processed volume, indicating a significant diversion issue that needs investigation.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-05</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/7 - Barun / Sean will deep dive this more details. Team will coordinate and followup.
|
||
11/6 Sean will deep dive this issue. Need to track daily package diversion counts and create Pareto chart of root causes.
|
||
11/5 FE Controls to deep dive - currently unsure if Grafana is counting the defects correctly.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">Other Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Ops, GEMS and MFO will review the floor layout to find opportunities to prevent jiffy divert on bypass lines</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Ops, GEMS and MFO will review the floor layout to find opportunities to prevent jiffy divert on bypass lines</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Connect with MFO to place D2Cs before palletized chutes and allow jiffy divert on palletized chutes. 11/07 - Layout deep dive in progress to identify divert opportunities for jiffys and prevent jiffy bypasses and jams caused by jiffys.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="Amazon">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="Amazon">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items (3)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">AWCS Multiple Destinations</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
<span class="age-days">29 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> AWCS was not sending multiple destinations for NC and Crossbelt in S02 Message</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/15 - Jamari Randle changed NC Config to have two destinations, still waiting for a change to Crossbelt Config</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Several jam points are inaccessible to RME/Ops for safety reasons, requiring vendor (DCS) callouts which significantly increases jam clear times. Long-term solutions include platforms post-peak, but for immediate peak support, WHS-approved ladders are being deployed on the mezzanine. Start Up team completed a site walkthrough on 10/28-10/29 with RME and safety. MTN6 RME will mark locations for Cotterman ladder deployment, with ladders being disassembled at ground level and reassembled on the mezzanine to cover 70-80% of elevated conveyance. Some areas will remain inaccessible due to space constraints. The site has two manual one-person lifts with six more on order for mezzanine deployment, with training scheduled next week. Operations is partnering with OE and RME to identify the top 10 jam locations and frequencies to develop a deployment strategy, while assessing whether additional vendor support is needed during the volume ramp.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
<span class="age-days">24 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Several jam points are inaccessible to RME/Ops for safety reasons, requiring vendor (DCS) callouts which significantly increases jam clear times. Long-term solutions include platforms post-peak, but for immediate peak support, WHS-approved ladders are being deployed on the mezzanine. Start Up team completed a site walkthrough on 10/28-10/29 with RME and safety. MTN6 RME will mark locations for Cotterman ladder deployment, with ladders being disassembled at ground level and reassembled on the mezzanine to cover 70-80% of elevated conveyance. Some areas will remain inaccessible due to space constraints. The site has two manual one-person lifts with six more on order for mezzanine deployment, with training scheduled next week. Operations is partnering with OE and RME to identify the top 10 jam locations and frequencies to develop a deployment strategy, while assessing whether additional vendor support is needed during the volume ramp.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-20</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 -
|
||
11/6 22-23 Cotterman ladders deployed (target was 25). Need to order more 12-step units. Two single-man lifts on order through Adam Gray. Additional lifts needed for center area and back platform.
|
||
11/5 16/25 ladders completed.
|
||
11/4 8/25 ladders have been setup on the Mezz.
|
||
11/3 25 Ladders are needed for Jam clearing on the Mezz. Currently all Ladders are assembled and must be broken down and brought up to the Mezz. Est. of 10 days completion.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The site is requesting a detailed schedule for vendor coverage to ensure 24/7 support availability.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
<span class="age-days">10 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The site is requesting a detailed schedule for vendor coverage to ensure 24/7 support availability.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-03</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Eli will provide once avail and final PO cut
|
||
11/6 POs issued for extended coverage through year-end. Updated escalation list needs redistribution to army and operations teams. OE schedule shared with OPS.
|
||
11/5 Angela, Eli, Anthony were not on the call for an update - will followup off line for expectation of coverage schedule.
|
||
11/3 PO's submitted for the Vendors to support through 12/21. Working on the schedule for OE.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="Amazon">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">A majority of the load balancing defects are being incorrectly attributed to disabled chutes when they're actually caused by "disabled" bypass belts. The team expected this metric to improve once all four virtual sorters became active, but the issue persists. Ops Engineering is now conducting a deep dive, pulling packages for container research to verify correct routing paths through the sorter. They need to confirm with Beumer that defect coding is properly registered in the system, and MFO will be contacted to rule out any mapping concerns that might be contributing to the misattribution.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> A majority of the load balancing defects are being incorrectly attributed to disabled chutes when they're actually caused by "disabled" bypass belts. The team expected this metric to improve once all four virtual sorters became active, but the issue persists. Ops Engineering is now conducting a deep dive, pulling packages for container research to verify correct routing paths through the sorter. They need to confirm with Beumer that defect coding is properly registered in the system, and MFO will be contacted to rule out any mapping concerns that might be contributing to the misattribution.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-03</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-07</p>
|
||
<p><strong>Status Updates:</strong> 11/6 Monitoring changes pending completion
|
||
11/5 due to the SEV2 on NIT sort 11/4, site would like to monitor for one more day.
|
||
11/4 Site wanted to monitor overnight to validate, if there are not any issues will be closed out 11/5.
|
||
11/3 Sorter Logic (Round Robin, Waterfall. etc.) is assigning packages to the bypass. Logic change should be implemented by 11/5.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="Amazon">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="Amazon">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (5)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">AWCS Multiple Destinations</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> AWCS was not sending multiple destinations for NC and Crossbelt in S02 Message</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/15 - Jamari Randle changed NC Config to have two destinations, still waiting for a change to Crossbelt Config</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The site is requesting a detailed schedule for vendor coverage to ensure 24/7 support availability.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The site is requesting a detailed schedule for vendor coverage to ensure 24/7 support availability.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-03</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Eli will provide once avail and final PO cut
|
||
11/6 POs issued for extended coverage through year-end. Updated escalation list needs redistribution to army and operations teams. OE schedule shared with OPS.
|
||
11/5 Angela, Eli, Anthony were not on the call for an update - will followup off line for expectation of coverage schedule.
|
||
11/3 PO's submitted for the Vendors to support through 12/21. Working on the schedule for OE.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Several jam points are inaccessible to RME/Ops for safety reasons, requiring vendor (DCS) callouts which significantly increases jam clear times. Long-term solutions include platforms post-peak, but for immediate peak support, WHS-approved ladders are being deployed on the mezzanine. Start Up team completed a site walkthrough on 10/28-10/29 with RME and safety. MTN6 RME will mark locations for Cotterman ladder deployment, with ladders being disassembled at ground level and reassembled on the mezzanine to cover 70-80% of elevated conveyance. Some areas will remain inaccessible due to space constraints. The site has two manual one-person lifts with six more on order for mezzanine deployment, with training scheduled next week. Operations is partnering with OE and RME to identify the top 10 jam locations and frequencies to develop a deployment strategy, while assessing whether additional vendor support is needed during the volume ramp.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Several jam points are inaccessible to RME/Ops for safety reasons, requiring vendor (DCS) callouts which significantly increases jam clear times. Long-term solutions include platforms post-peak, but for immediate peak support, WHS-approved ladders are being deployed on the mezzanine. Start Up team completed a site walkthrough on 10/28-10/29 with RME and safety. MTN6 RME will mark locations for Cotterman ladder deployment, with ladders being disassembled at ground level and reassembled on the mezzanine to cover 70-80% of elevated conveyance. Some areas will remain inaccessible due to space constraints. The site has two manual one-person lifts with six more on order for mezzanine deployment, with training scheduled next week. Operations is partnering with OE and RME to identify the top 10 jam locations and frequencies to develop a deployment strategy, while assessing whether additional vendor support is needed during the volume ramp.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-20</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 -
|
||
11/6 22-23 Cotterman ladders deployed (target was 25). Need to order more 12-step units. Two single-man lifts on order through Adam Gray. Additional lifts needed for center area and back platform.
|
||
11/5 16/25 ladders completed.
|
||
11/4 8/25 ladders have been setup on the Mezz.
|
||
11/3 25 Ladders are needed for Jam clearing on the Mezz. Currently all Ladders are assembled and must be broken down and brought up to the Mezz. Est. of 10 days completion.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Deep dive metrics analysis has revealed that between 40,000 to 50,000 defects are diverting to PS daily. Using Grafana Lane watch, the data shows that Jackpot chutes (11001, 12098, 13003, 14086) are receiving 30% to 50% of the site's daily processed volume, indicating a significant diversion issue that needs investigation.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Deep dive metrics analysis has revealed that between 40,000 to 50,000 defects are diverting to PS daily. Using Grafana Lane watch, the data shows that Jackpot chutes (11001, 12098, 13003, 14086) are receiving 30% to 50% of the site's daily processed volume, indicating a significant diversion issue that needs investigation.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-05</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/7 - Barun / Sean will deep dive this more details. Team will coordinate and followup.
|
||
11/6 Sean will deep dive this issue. Need to track daily package diversion counts and create Pareto chart of root causes.
|
||
11/5 FE Controls to deep dive - currently unsure if Grafana is counting the defects correctly.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Ops, GEMS and MFO will review the floor layout to find opportunities to prevent jiffy divert on bypass lines</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Ops, GEMS and MFO will review the floor layout to find opportunities to prevent jiffy divert on bypass lines</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Connect with MFO to place D2Cs before palletized chutes and allow jiffy divert on palletized chutes. 11/07 - Layout deep dive in progress to identify divert opportunities for jiffys and prevent jiffy bypasses and jams caused by jiffys.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="Autstand">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">Autstand</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">100</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">76</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">10</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">14</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'Autstand')" data-status="all">All (100)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand')" data-status="oldest_unaddressed">Oldest Unaddressed (3)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand')" data-status="closed">Closed (76)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand')" data-status="monitor">Monitor (10)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand')" data-status="incomplete">Incomplete (14)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="Autstand">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Critical Priority (14 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi-Auto Exception Arm Logic</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Exception chute arm disengaged prior to all cartons being filled on semi-autos. Logic needs to be amended. Apply to all areas</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> 10/14 - Interim measure in place to force arm extension, Kevin working on updating logic at all VS fixed 10/14</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS Conveyor chute clearing Issues</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Chute/conveyor beacon at the top of the problem solve chutes directly off of the sorter are not automatically clearing when the downstream belts are cleared. Indicating that the PS chutes are full or unavailable for packages to divert</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-17</p>
|
||
<p><strong>Status Updates:</strong> complete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Tipper timer</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Adjust tipper logic to prevent two tippers from dumping at the same time and jamming the line</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> 10/16 - in progress... ECD : 10/20 (dtw needed) 10/19 - inprocess will be complete by EOD
|
||
KK 10/19 - Fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA Accurate Status Reads</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Update SCADA status accuracy with info sent from Beumer</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> 10/14 - All necessary information received from Beumer to execute change
|
||
10/16 - closed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NC boxes are diverting to xbelt causing jams particullary at bypass curves</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> 10/17 - Ian adjusted the 3 merges on MCM2 to max length to xbelt to 42" Monitor and update MCM01 flow splitter</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Noncon detection length reduced to 41"</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Over-width noncons diverting to crossbelt</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Packages that are over-width that should pass through to noncon are being diverted at the inbound flow splitter - causing jams (KK 11/7)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-09</p>
|
||
<p><strong>Status Updates:</strong> KK 11/7 - We are investigating how to add width into the divert decision at inbound.
|
||
|
||
KK 11/8 - Robin made the hardware/software updates to PS1/2/3, will continue the rest tomorrow
|
||
|
||
KK 11/10 - Over-width detection has been added to all PS lines as of last night</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Noncons being diverted to PS lines</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Noncons are being diverted to PS lanes. Happens sporadically, not systemically. Seems to occur primarily at PS2, with some reports of it happening at PS7. (KK 11/10 - this has been occurring but never formally logged)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-10</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/10 - Still unsure why this happening. Hard to evaluate whether any potential fixes we apply are effective without data. Most occurences come anecdotally and with pictures. We can observe PS2 splitter for 30 mins and watch dozens of noncons pass through correctly. Igor and Robin are both still actively investigating the issue.
|
||
|
||
KK 11/11 - Duplicate now that Amazon updated this list with their internal punchlist. Row 199. Closing this one.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Replicate logic timers from semi VS-D to the rest of the semis</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Logic timers from semi-auto at all virtual sorters need to be adjusted</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/16 - fix applied monitor as VS become active</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jiffys to noncon</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Jiffys are getting to noncon causing jams and potential damage to intralox sorters (KK 11/7)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/7 - Observed inbound flowsplitter to see why jiffys were not being diverted. Findings were that very light jiffys or jiffys with non-flat topology could not physically be diverted successfully. The tracking PEs and logic worked as it should. The diverting mechanism actuates when the jiffy traversed the divert point.
|
||
|
||
In the case of light jiffys, they other did not have enough weight to engage with the roller bed to divert, or they started to divert but catch air which then reduces downward pressure and reduces engagement with divert mechanism.
|
||
|
||
In the case of non-flat jiffy (convex or circular footprint), the jiffy tumbled or rolled around when trying to divert.
|
||
|
||
In both cases, we grabbed several jiffys that failed to divert due to physics and re-inducted them, to prove that the logic was picking them up and attempting to divert them, and in some cases they were diverted.
|
||
|
||
I have reached out to DCS and intralox to confirm what the minimum recommended MTBH weight is for the inbound intralox flow splitters.
|
||
|
||
KK 11/8 - Talked with Deepak about potential solutions, he suggest having a fixed divert on each noncon sorter and divert anything less than noncon length there (including jiffys). He said he would follow up internally and let us know how to proceed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA is being updated through cooperation between Autstand and Firm Engineering across all three Autstand sites (SAT9, MTN6, CNO8). Operations has identified Active Alarms as a barrier, as the alarms are backlogged and not clearing from the Active Alarms tab. Additionally, the Statistics/Status tab is currently unavailable, limiting system monitoring capabilities.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> SCADA is being updated through cooperation between Autstand and Firm Engineering across all three Autstand sites (SAT9, MTN6, CNO8). Operations has identified Active Alarms as a barrier, as the alarms are backlogged and not clearing from the Active Alarms tab. Additionally, the Statistics/Status tab is currently unavailable, limiting system monitoring capabilities.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Monoriting
|
||
11/7 - Autstand pushed updates for sorter statistics. Needs validation before closing this item.
|
||
11/4 @deepak requested a list of the Metrics that are needed and currently not available. Expo will be onsite 11/7 and will compile a list.
|
||
11/3 Austand working through update improving user interface.
|
||
|
||
KK 11/11 - Root cause identified last night, patch to be rolled out today. SCADA server running out of resources, causing it to become unresponsive and show the wrong statuses. Scada 2.0 template bloat and ineffecient data/alarm handling on our end will be addressed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The 3 to 1 merge is merging side by side creating jams downstream. This could also lead to double packages getting inducted to the sorter.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The 3 to 1 merge is merging side by side creating jams downstream. This could also lead to double packages getting inducted to the sorter.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-08</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/8 - issue added from Controls deep diving on site. Vendor has updated the merge logic using a MCM. Issue to be monitored. Video attached.
|
||
|
||
KK 11/11 - There is no systemic issue that we are aware of. There are two specific belts, one on UL9 and UL14 that under certain circumstances can cause a side-by-side because they are behaving errantly. These two belts do not stop or start at the speed which we need for the logic to work. We have already tried swapping the VFD and brake resistor, and verified the logic. We discussed with DCS and they assured us that it could not be a mechanical issue.
|
||
|
||
We have seen every day packages being unloaded side-by-side directly from the trailer, and packages loaded on top of eachother. Frankly, I think most of the side-by-sides are caused by this. Not to say that we have occurences due to the merge, but it is not the only factor.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non-con packages are getting diverted to auto induct causing jams at the inducts and too many reversals by the auto induct.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non-con packages are getting diverted to auto induct causing jams at the inducts and too many reversals by the auto induct.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-08</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10- Autstand added logic to measure width in addition to length to identify packages that may have rotated orientation.
|
||
`1/09 - deep dive from controls shows measurements are not reliable and lengths are not calculated accurately causing in-consistent behavior at the flow splitter.
|
||
|
||
KK 11/10 - Still unsure why this happening. Hard to evaluate whether any potential fixes we apply are effective without data. Most occurences come anecdotally and with pictures. We can observe PS2 splitter for 30 mins and watch dozens of noncons pass through correctly. Igor and Robin are both still actively investigating the issue.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam beacons at the merge are not showing jams. It is happening across all merges.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Jam beacons at the merge are not showing jams. It is happening across all merges.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-08</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Autstand adjusted the PE- monitoring , 11/09 - After further inspection all the jam beacons are reporting the wrong place. Jam happened at the 7-1 merge, the beacon light up but jam cannot be found in that location.picture attached for reference.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non con package to jackppt</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Packages going directly to jackpot, jam the sorter and affect overall flow</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-11</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/11 - Issue first occurred last night at the end of DAY sort. Igor cam and investigated, noticed high number of unexpected package and lost tracking. Identified some problem PEs and adjusted.
|
||
|
||
The issue occurred again at the beginning of DAY sort 11/11. Igor came in and is still investigating. The issue is transient.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (68 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Problem Solve dead rollers</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> First few rollers not able to be engaged due to missing part on both Problem Solve lines</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - First problem solve line complete, second will be complete by EOD</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam Reset Button needed at end of NC Jackpots</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> There is no reset at the end of the NC sorters need to be at proximity of jam clearing</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> 10/17 - buttons there, programimed, waiting on bracket</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam Reset buttons on Bulk divert platforms to be relocated</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> JR button is behind the saefty fencing move to outside of fencingv (all areas)</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 - downtime window needed. 10/21 - to be scheduled
|
||
KK 11/7 - I learned that this was done almost two weeks ago actually, closing this item</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Flow Splitter Verification</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Conveyable cartons are entering the non-con at a high rate. Verify all 7 flow splitters are working correctly</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 -- adjusted still fine tuning. may reduce nc length..TBD</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NC Dim Data</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> AutStand not sending DIM data in S01 Message</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/15 - Matt Specht fix mid sort
|
||
10/17 - COMPLETE</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam Reset NC End of Sorter</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Need to add jam reset pb for end of sorter jam pe, currently the only reset is at the head of the nc sorter</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> duplicate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">"Destination Not Attempted" Reason Code</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Receiving "Destination Not Attempted" in the wrong use case/scenario for the NC Sorter, see screenshot</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-21</p>
|
||
<p><strong>Status Updates:</strong> 10/17 -- follow up
|
||
KK 10/21 - Based on container research data from Sherri, this reason code is no longer being sent in our S04</p>
|
||
<p><strong>Image:</strong> image.png</p>
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS lines stop packages at the top of the line, on the first station. It should push the packages to the last station Jackpot probem solve</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> 10/17 fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Still seeing Lost Container / No Reads in NC Jackpot</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> 10/16- Reviewed logic/flow. Updated installed at noon. Will be monitoring
|
||
KK 10/27 - Issue seems to be resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">First chute orange lights keeps turning on without pakages blocking any sensors semi auto vs-d</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> Fixed, realigned PE</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Flashing and steady blue light on a chute without any package present S014020, S014018</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> Please ensure the cart is loaded centered in the chute, too far to the left or right, or skewed will result in the overhead sensor will read the frame of the cart and prematurely trigger full
|
||
10/17 - fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Flashing Green light on D2C , start button doesn't work S014041</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> Fixed - bad button, has been replaced</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">non- con packages still has divert issues packages going straight to jackpot</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> Temporary buttons in placed at the end of each sorter, brackets pending</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Scada Map not showing cameras</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> SCADA is showing cameras, the live feeds don't work at the moment, pending AMZ response for configuration (I contacted Davo and JC from ops eng for this)
|
||
10/17 fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Scada Map: showing stopped but actually running C</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> 10/17 - need more info
|
||
KK 10/18 - Need more info
|
||
KK 10/21 - No clarification received
|
||
KK 10/27 - No clarification received, closing this item</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS lines stop packages at the top of the line, on the first station. It should push the packages to the last station.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> Fixed - corrected flow control on problem solve rollers</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Still seeing Lost Container / No Reads in NC Jackpot as of 1044</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> Flow/assignment issue - to be addressed by Sherri (AMZ) and MFO today 11/1
|
||
10/17 monitor
|
||
KK 10/27 - Issue seems to be resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">206 - 207 max reach giving us false signals its green on skada but not operational</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> Need further clarification 10/19 - completed
|
||
10/19 KK - Done</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Take away line from shuttle tipper side pan is loose and causing jams/PE mis alignment</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> 10/17 DCS investigated and found the PEs on one of the tipper takeaways was installed/attached incorrectly. Autstand was advised to fix PEs</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> KK 10/27 - Investigated, found no issues</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Packages not diverting on the correct intralox</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Need further clarification
|
||
KK 10/21 - No clarification received - closed as duplicate (Row 120)</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Label auto inducts</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-20</p>
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">S012075 unavailable</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S012075</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> KK 10/19 - Done</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">VSD- S014020 BLINKING BLUE WHILE CHUTE IS EMPTY</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Virtual sort- D</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> IH 10/18 - Confirmed functionality of the chute.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">VSD- S014018 SOLID BLUE WHILE CHUTE IS EMPTY</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Virtual sort- D</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> IH 10/18 - Confirmed functionality of the chute.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">D2C S014041 flashing green + activation button not illuminating</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Virtual sort D D2C S014041</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Problem Solve rollers do not correctly inch-and-store packages, causing line to jam prematurely</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/17 - PRS photoeyes have been re-aligned and tightened</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA: We need some type of refrence in SCADA. Suggest adding dock doors that correlate with their belt</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Flow Desk</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-07</p>
|
||
<p><strong>Status Updates:</strong> KK 11/7 - Added dock door numbers to screens</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Run-up is not enabled on Problem solve collection belts. They all stop when the photoeye at the rollers is blocked.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Problem solve</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/17 - PRS photoeyes have been re-aligned and tightened</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Potential PE issue at the problem solve rollers right when the chutes level off. 300 side.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> BC problem solve</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/17 - PRS photoeyes have been re-aligned and tightened</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA: scada camera view from main map wont allow user to pan camera angles when clicked onto</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Flow Desk</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Adjusting the camera angle is not possible from SCADA. Can be done by accessing the camera directly with its IP address.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS9-3CH2 - located by semi induct C. Blue light actived with no packages</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Semi induct C</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> MC: Blue Light was NOT on when investigated, still went ahead to realign better PE/teach again (10/18/25)</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">semi induct c chute 2 Flase blue light PE needs adjusted</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> MC: Blue Light was NOT on when investigated, still went ahead to realign better PE/teach again (10/18/25)</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">IBNC splitting sending packages to NC that are within the crossbelt MTBH</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Inbound</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-16</p>
|
||
<p><strong>Status Updates:</strong> KK 10/16 - Splitter logic adjusted</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">D2C Chutes are full blue lighting 8 inches short of the go cart full line</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> VS-D (But I assume all virtual sorters)</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-16</p>
|
||
<p><strong>Status Updates:</strong> KK 10/16 - Raised ALL D2C Full height 6-8" above last setting</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">chute stays green even when chute is full</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Chute S014073</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> IH 10/18 Resolved. IO Mapping issue.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non- con packages coming down to lanes</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> VS-D</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Noncon detection length reduced to 41"</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Scada - label each line ex. UL13 , UL14 ect.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Inbound 3-1 merges</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> IH 10/19 SCADA Updated</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS11-11CH6NC Intralox Sorter (S02)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> PS11-11CH6NC Intralox Sorter (S02)</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/27 - Need clarification. I don't see the relation between PS11-11 and the intralox sorter.
|
||
KK 11/10 - Did not receive clarification, closing this item</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Blue light for semi induct D is on when chute is empty</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> PS11-11CH6NC</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Realigned and trained photoeye</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Need 1 button to turn on ALL inducts. I am having to turn them on one by one</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Buemer scada</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Our global start button is confirmed to start all autStand conveyors and Beumer CMC/SMC conveyors, only if they are not faulted.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non-Con running through main sorter causing system to shutdown; Non-con packages not diverting to Non-cons sorter taking up carriers on Sorter</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Main Sorter</p>
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Noncon detection length reduced to 41"</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">DTW8/CLE5 Non-Con packages not diverting to chutes; running straight through jackpot</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non-Con sorter</p>
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - MFO issue
|
||
KK 10/19 - Not MFO, need to deep dive tracking/diverting/etc
|
||
KK 10/20 - Identified potential issue with a photoeye missing incoming packages at scan tunnel induct, which manifest as unknown/unexpected packages and causing some packages to go off-the-end. We adjusted this sensor and are monitoring. Initial observations seem promising
|
||
KK 10/27 - Resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SEMI-D uneven flow of packages to each chute</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> SEMI-D</p>
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Logic continually being optmized (monitor)
|
||
KK 10/27 - This is a duplicate item related to bulk induct shutes (row 6), I will close it</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Clean up SCADA Active Jams to not show false jams ex BYBA-15 /BYBD-14</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/21 - Aware of a couple "stuck" alarms - still investigating why RS 10/30 - This issue seems to be fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Disable jam pe's that are to be removed (bulk chutes)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Disabled, pending physical removal</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Evaluate jam logic /die back on bypasses.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> getting "false jams" of box stopped in from of PE when belt stops. Bypass jams are difficult to access need to minimize them</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-19</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> KK 10/19 - Verified that it is not being caused by runup logic, need to continue to monitor
|
||
KK 10/27 - False jams seemed to have stopped being as frequent. There is still no runup logic causing this.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA performance issue</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> report export crashed system</p>
|
||
|
||
<p><strong>Date Completed:</strong> 2025-11-04</p>
|
||
<p><strong>Status Updates:</strong> 11/1 RC - SCADA was updated to improve performance yesterday NIGHT.
|
||
KK 11/4 - Assuming this is related to SCADA crashing when trying to export large amounts of data (like a week of alarms). We addressed, just tested and it did not crash.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">3:1 merge code update</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> mcm02 by monday 11/4. mcm01 ul 1-3 done. mcm01 complete.</p>
|
||
|
||
<p><strong>Date Completed:</strong> 2025-11-09</p>
|
||
<p><strong>Status Updates:</strong> 11/3 - no update... Igor at BNA8
|
||
KK 11/6 - Plan sent to AMZ, targetting to execute at noon on 11/8
|
||
KK 11/8 - Lack of downtime today prevented us from executing, we are replanning for tomorrow 6-8AM downtime, operations put a building volume cap in place
|
||
KK 11/10 - This was complete yesterday, marking as Complete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Raise the fill height ob the DTC's approx 2 "</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-11-04</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-05</p>
|
||
<p><strong>Status Updates:</strong> RC 11/6 - All DTC chutes' full heights have been raised 6".</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS8-5 Jammed but not showing on SCADA</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> KK 11/6 - Per Chris' Twi sort 11.6 report - PS8-5 jammed but did not animate on SCADA</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-06</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/12 - Fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NCP1-6-TPE1 did not alarm correctly on SCADA when jammed</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Jiffy got to noncon and stuck in a T-plate causing NCP1-6-TPE1 to jam, but this did not animate at all on SCADA, leading to a slower than typical resolution (KK 11/7)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> RC 11/8 - Incorrectly in what way?
|
||
KK 11/8 - Fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Aligner vertical belts running when rollers are jammed</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Dead rollers on one of the aligners caused the aligners to jam and stop running, but the vertical belt kept running - damaging the vertical belt</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-10</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-10</p>
|
||
<p><strong>Status Updates:</strong> KK 11/10 - I modified the logic to work this way. If downstream is running, that allows the rollers to run. If the rollers are running, then the vertical belt is allowed to run. Previously, if downstream was running, both the rollers and vertical belt were allowed to run.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Fluid Load Lane displays as "Lane Unavailable" when the FLL is actually operational (blue lit).</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Fluid Load Lane displays as "Lane Unavailable" when the FLL is actually operational (blue lit).</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-09</p>
|
||
<p><strong>Status Updates:</strong> 11/07 - D99 - messages are not correct. Reporting lane unavilable. Beumer needs to update messages.
|
||
11/6 Past due. Logic changes were attempted yesterday but didn't work and were rolled back. Now testing on one lane (BYCD 2). Autstand (integrator) is making code changes with internal controls team monitoring. Results expected tomorrow.
|
||
11/5 due to the SEV2 on NIT sort 11/4, site would like to monitor for one more day.
|
||
11/4 Implemented logic change 11/4 - monitoring.through 11/5 and will be closed if no new issues are reported.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Bypass shows as Lane Unavailable/Non-operational when the Bypass is at capacity (full/blue lit).</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Bypass shows as Lane Unavailable/Non-operational when the Bypass is at capacity (full/blue lit).</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-09</p>
|
||
<p><strong>Status Updates:</strong> 11/07 - D99 messages need to be updated. Beumer needs to update the messages.
|
||
11/6 Similar to MTN6-002, bypass lines being optimized with inch in store logic to maintain product flow and reduce lane unavailables. Testing in progress
|
||
11/5 Testing the run up logic was not successful, @davaoste is waiting for next steps from the vendor.
|
||
11/4 Bypass Logic will be updated on one sorter to test - if successful, the defect will now show as lane full instead of Lane unavailable and will roll out to the rest of the bypasses by 11/7 if no issues are found in the test period.
|
||
11/3 Once FLL change has been monitored and confirmed, Logic change will be rolled out to the bypasses. Need to rollout separately to have time to monitor clean data before rolling out the second change.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Merge optimization is underway with the non-con specification temporarily reduced from 47" to 42" while Autstand optimizes the merges. The inducts to Virtual sorters A and C (UL1-12) have been completed. Once all inducts are optimized, the non-con spec will be expanded back to 47". During this optimization process, it's safer to route smaller packages to non-con rather than sending larger packages to the crossbelt system.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Merge optimization is underway with the non-con specification temporarily reduced from 47" to 42" while Autstand optimizes the merges. The inducts to Virtual sorters A and C (UL1-12) have been completed. Once all inducts are optimized, the non-con spec will be expanded back to 47". During this optimization process, it's safer to route smaller packages to non-con rather than sending larger packages to the crossbelt system.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - In progress
|
||
11/07 - Improvement made in flow splitters with proper diverts. However, square boxes are still creating jams. Logic to prevent small boxes going to NC and NC going to XB has been fixed. 11/6 Egor evaluating timing issues with 3-to-1 merge logic. Only first 3 merges updated, 4 remaining need logic updates. Gapping/pitching incomplete on MCM2-1, scheduled for Saturday.
|
||
11/5 Will coordinate with OPS for schedule of DT windows for each IB lane to make the update. Will be completed by 11/7
|
||
11/4 Testing completed,, will rollout 1 IB lane at a time to be completed by 11/5.
|
||
11/3 Logic change to reduce 42" until merge logic optimization is complete.
|
||
KK 11/11 - To be clear, we had to reduce to 42" because the auto induct will reject anything greater than that. It will not be raised back to 47". Discussed on the daily call today - moving to design rather than mechanical/controls.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Logic for Semi induct D is off very low throughput see video</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Semi Auto D induct</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Tweaking logic, continually adding optmizations</p>
|
||
<p><strong>Image:</strong> see video in comments</p>
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">One major issue and one minor issue with the non-con system:
|
||
No-reads are really frequent
|
||
The PLC is not reporting S04 message divert fails properly (no reads to jackpot, lost container, failed to divert, wrong buildings)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> NON con sorter 1 and 2 not diverting</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - For the whole sort yesterday we had 13 No Reads out of 500 inducted (2.6%) we will see what can be done to reduce this.
|
||
IH 10/19 Datalogic & PLC update conducted. Will continue to monitor.
|
||
KK 11/30 - Fixed the "Unknown" S04 message, verified with AWCS data</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Bypass improvements</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Bypass showing lane unavailable when not running, instead of full. Bypass shows relatively high unavailable rate. (KK 11/7 - Writing this descrpition retroactively, I am not sure who began tracking this issue or when)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-03</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/4 - All bypasses were made to show "Full" rather than "Unavailable" when the bypass was not running
|
||
KK 11/5 - Tried enabling run-up for a bypass lane, issue with logic, caused jams, rolled back
|
||
KK 11/7 - Run-up logic enabled on whole BYDC during downtime, will monitor upcoming sort
|
||
KK 11/9 - Run-up for all bypass belts enabled, caught a few cases where there were jams, we fixed the logic.
|
||
KK 11/10 - Almost all bypass jams dropped from the jam hitlist today, a good sign.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Sorter statistics on SCADA</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Add crossbelt sorter statistics to ignition SCADA (KK 11/7 - Writing this descrpition retroactively, I am not sure who began tracking this issue or when)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-03</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/7 - Updated statistics section of SCADA to show sorter stats before 11/7 DAY sort. First time testing with live data, there are some bugs to address
|
||
KK 11/8 - Updated SCADA to address sorter statistic bug, looks correct now, pending validation by Amazon</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Update SCADA to show inch and store status of conveyors with such functionality</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Update SCADA to show inch and store conveyors as YELLOW while inch and store is enabled and BLUE while inch and store is full (KK 11/7)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/9 - Done for all FL lanes and PRS lanes, bulk to follow</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS8-6 flow splitter eating packages</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> PS8-6 flow splitter is sucking in packages at the discharge end (KK 11/7)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/8 - Observed this for about 2 hours during TWI sort. I saw the scenario that could lead to a package getting sucked in. 50% physics and 50% logic. Very light jiffys tend to ignore the divert rollers, just like inbound. I modified the PS8-5 splitter logic and PS8-8 flow logic in order to mitigate this happening. Ultimately I think it is not 100% preventable, except for maybe waterfalling onto the conveyor directly</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Encoder failure (4x) + 2 x</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> UL8-7 UL11-7 Problem with port on APF</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-10</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/23 ST soluton is changing the port... LT reseach with Rockwell 10/29 - Rockwell to send engineer to test system 10/30 ; 10/30 RC - Rockwell visit not happening today. TBD. 10/30 - looking to send "capable engineer" to address engineer. today another encoder failed UL18-10 (all merge stop - 20 min swapping) 11/3- Rockwell scheduled to be on site 11/6.
|
||
|
||
KK 11/7 - Rockwell came to site and investigated, but ultimately was not able to deterine the root cause of the issue, they collected data which they will use at their lab to try to recreate the issue and investigate further.
|
||
|
||
KK 11/8 - Rockwell suggested to try a different setting on the encoders, we are targetting 11/10 to do this.
|
||
|
||
KK 11/10 - Not enough downtime during the day to do the change
|
||
|
||
KK 11/12 - We are doing the suggested change on UL14 during the DAY/TWI downtime window. Will evaluate for the next sort.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">7:1 merge code update</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/10 - Will not happen before peak</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Estops are getting damaged on the UL lane</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> UL16-1, UL15-3, UL10-2 (both sides) UL8-1 , UL7-3, UL6-1 protect or relocate devices</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-04</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/10</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Fix tippers faulting mid-dump sequence</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Tippers that are flow-stopped during the dumping sequence will remain raised and fault after a period of inactivity.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-06</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/7 - It seems this only started happening once the code from Pioneer was "updated". Requires further investigation - as holding a tipper queued up and ready to tip as soon as the belt became available has always been standard practice.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PE not showing on scada/beacon</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Level (50/100% fullness) PEs are not showing in SCADA or in the beacons — tested on chutes DD119, DD319, DD320, and DD321 — which indicates a system issue affecting both SCADA and the beacon network.
|
||
|
||
There are also instances where SCADA displays blue (package detected) while the beacon does not, even though no package is physically present, suggesting inconsistent signal behavior between both systems.
|
||
|
||
Additionally, several PE connectors were found disconnected from the cable box, which could be contributing to the issue.
|
||
|
||
Issue shown to Carlos Radielli.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-10</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/11 - Root cause identified last night, patch to be rolled out today. SCADA server running out of resources, causing it to become unresponsive and show the wrong statuses. Scada 2.0 template bloat and ineffecient data/alarm handling on our end will be addressed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA issues see SCADA Tab</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Validating SCADA accuracy</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-11</p>
|
||
|
||
<p><strong>Status Updates:</strong> Outlining SCADA discrepencies on week of 11/10.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">S013064 – Blue indicator light remained active without packages present, suggesting a possible sensor or control fault; RME was called to investigate issue.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S013064 – Blue indicator light remained active without packages present, suggesting a possible sensor or control fault; RME was called to investigate issue. (Taken from operations report for 11/11 MOR sort - KK 11/12)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-11</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/12 - This was reported to us on 11/12</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">Low Priority (6 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Chute 14041 Enable Issues</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> DTC chute won't stay enabled even with cart in correct position and button pressed</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">VS-D, S01400 Pallet Chute Beacons - False Fullness</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Chute fullness indicator beacon illuminated incorrectly, check all chutes but specifically S014020, S014018</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/15</p>
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi-Auto Jam Beacons</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> remove jam PE at chute</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-28</p>
|
||
<p><strong>Status Updates:</strong> 10/19 PE functionality diabled.. hardware removal to be scheduled TBD
|
||
KK 11/4 - hareware was removed on 10/28</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The panel has a blinking jam indicator active all the time</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The panel has a blinking jam indicator active all the time</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Autstand advised of the observation
|
||
11/09 - Issue logged
|
||
KK 11/11 - This indicator is not blinking as I write this message. Did the person who report this check if there was actually a jam in that system..? I went and checked now and it is off. Closing the item</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Run up logic needs to be activated all across the site. When a conveyor stops their signal drops for all the conveyor behind creating unnecessary start stop and not allowing for accumulation.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Run up logic needs to be activated all across the site. When a conveyor stops their signal drops for all the conveyor behind creating unnecessary start stop and not allowing for accumulation.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/09 - attached video for reference. Run up logic needs to be enabled on all conveyors to allow packages to accumulate without creating a lot of empty space impacting throughput. When the inducts start the system should be able to keep up with induct rates. The video also shows a regular package trying to divert.
|
||
|
||
KK 11/12 - Runup was enabled in MCM03, so that when the NC sorter is down, noncon packages can continue past the inbound flow splitters and queue up as. This should help inbound run longer when noncon goes down. Any other runup areas need to be discussed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">When conveyor are starting they start all at ones and that also contributes to a start stop behavior. A cascade start is suggested</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> When conveyor are starting they start all at ones and that also contributes to a start stop behavior. A cascade start is suggested</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/09 - cascade logic will allow the system not having continuous start stop behavior. Currently there is no cascade start sequence on the conveyors. By adding cascade delay while starting up the system can minimize the number of start and stops.
|
||
|
||
KK 11/12 - Need clarification on what exactly the ask here is</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">Other Priority (6 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi-Auto Chute fullness PE Height</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Adjust 50% and 100% Full PE locations to better optimize the load logic for semi-auto inducts</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> 10/17 - load logic was adjusted... monitor PE response.
|
||
KK 10/27 - This is a duplicate item related to bulk induct shutes (row 6), I will close it</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam Cam visibility in SCADA</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Autstand needs to set up passwords/remove pw for it to work in the scada</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> complete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS11_11_JR3</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Jam Reset PB is flashing sporadically</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> 10/17 - in process
|
||
10/18 KK - Done</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">S013089 Blue Beacon</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Need to investigate ZMX Sensor, alignment causing false fullness indication</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Done, beacon replaced</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Bypasses are "going to sleep"</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> 10/17 - there is no sleep or energy mgt on the bypasses Will die back if induct is not running</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Punch holes on bypass photo eyes are damaging packages</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Punch holes on bypass photo eyes are damaging packages</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/07 - Punch holes on bypass were reviewed and pictures taken. Work in progress
|
||
KK 11/11 - Nerio on site will evaluate, seems to be an issue mostly around curves and long packages.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">No Priority (6 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">False blue lights</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S014020 (AUTO-CHUTE4020) , S014018 (AUTO-CHUTE4018)</p>
|
||
<p><strong>Date Identified:</strong> 10/25/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> duplicate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA: Need a way to click onto jammed area on main page to see where the jam is located and how to get there</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Flow Desk</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 - That exists. Sherri showed several team members an dRME how to do this</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non con diverts going down - becon alluminating but belt still running</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> interlock</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Need clarification
|
||
KK 10/19 - Closed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non Con flow issues -- missorts to S02207</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> KK 10/27 - Resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">gap control at non con sorter.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> code change/ help with box tracking.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-30</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-04</p>
|
||
<p><strong>Status Updates:</strong> working on it today. /tomorrow
|
||
KK 11/4 - 0 gap errors since logic update, closing this item</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">DTC chutes on VS-B is randomly disabling</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/30 RC - Is this still an issue? Chute code was updated to add a debounce period for registering a cart removal. This should mitigate any false removals caused by jiffies triggering the sensor while falling into the cart.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="Autstand">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="Autstand">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items (3)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Encoder failure (4x) + 2 x</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
<span class="age-days">34 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> UL8-7 UL11-7 Problem with port on APF</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-10</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/23 ST soluton is changing the port... LT reseach with Rockwell 10/29 - Rockwell to send engineer to test system 10/30 ; 10/30 RC - Rockwell visit not happening today. TBD. 10/30 - looking to send "capable engineer" to address engineer. today another encoder failed UL18-10 (all merge stop - 20 min swapping) 11/3- Rockwell scheduled to be on site 11/6.
|
||
|
||
KK 11/7 - Rockwell came to site and investigated, but ultimately was not able to deterine the root cause of the issue, they collected data which they will use at their lab to try to recreate the issue and investigate further.
|
||
|
||
KK 11/8 - Rockwell suggested to try a different setting on the encoders, we are targetting 11/10 to do this.
|
||
|
||
KK 11/10 - Not enough downtime during the day to do the change
|
||
|
||
KK 11/12 - We are doing the suggested change on UL14 during the DAY/TWI downtime window. Will evaluate for the next sort.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA is being updated through cooperation between Autstand and Firm Engineering across all three Autstand sites (SAT9, MTN6, CNO8). Operations has identified Active Alarms as a barrier, as the alarms are backlogged and not clearing from the Active Alarms tab. Additionally, the Statistics/Status tab is currently unavailable, limiting system monitoring capabilities.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
<span class="age-days">29 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> SCADA is being updated through cooperation between Autstand and Firm Engineering across all three Autstand sites (SAT9, MTN6, CNO8). Operations has identified Active Alarms as a barrier, as the alarms are backlogged and not clearing from the Active Alarms tab. Additionally, the Statistics/Status tab is currently unavailable, limiting system monitoring capabilities.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Monoriting
|
||
11/7 - Autstand pushed updates for sorter statistics. Needs validation before closing this item.
|
||
11/4 @deepak requested a list of the Metrics that are needed and currently not available. Expo will be onsite 11/7 and will compile a list.
|
||
11/3 Austand working through update improving user interface.
|
||
|
||
KK 11/11 - Root cause identified last night, patch to be rolled out today. SCADA server running out of resources, causing it to become unresponsive and show the wrong statuses. Scada 2.0 template bloat and ineffecient data/alarm handling on our end will be addressed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Estops are getting damaged on the UL lane</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
<span class="age-days">9 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> UL16-1, UL15-3, UL10-2 (both sides) UL8-1 , UL7-3, UL6-1 protect or relocate devices</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-04</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/10</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="Autstand">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (76)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi-Auto Exception Arm Logic</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Exception chute arm disengaged prior to all cartons being filled on semi-autos. Logic needs to be amended. Apply to all areas</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> 10/14 - Interim measure in place to force arm extension, Kevin working on updating logic at all VS fixed 10/14</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS Conveyor chute clearing Issues</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Chute/conveyor beacon at the top of the problem solve chutes directly off of the sorter are not automatically clearing when the downstream belts are cleared. Indicating that the PS chutes are full or unavailable for packages to divert</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-17</p>
|
||
<p><strong>Status Updates:</strong> complete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Tipper timer</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Adjust tipper logic to prevent two tippers from dumping at the same time and jamming the line</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> 10/16 - in progress... ECD : 10/20 (dtw needed) 10/19 - inprocess will be complete by EOD
|
||
KK 10/19 - Fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA Accurate Status Reads</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Update SCADA status accuracy with info sent from Beumer</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> 10/14 - All necessary information received from Beumer to execute change
|
||
10/16 - closed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Problem Solve dead rollers</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> First few rollers not able to be engaged due to missing part on both Problem Solve lines</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - First problem solve line complete, second will be complete by EOD</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam Reset Button needed at end of NC Jackpots</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> There is no reset at the end of the NC sorters need to be at proximity of jam clearing</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> 10/17 - buttons there, programimed, waiting on bracket</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam Reset buttons on Bulk divert platforms to be relocated</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> JR button is behind the saefty fencing move to outside of fencingv (all areas)</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 - downtime window needed. 10/21 - to be scheduled
|
||
KK 11/7 - I learned that this was done almost two weeks ago actually, closing this item</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Flow Splitter Verification</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Conveyable cartons are entering the non-con at a high rate. Verify all 7 flow splitters are working correctly</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 -- adjusted still fine tuning. may reduce nc length..TBD</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi-Auto Chute fullness PE Height</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Adjust 50% and 100% Full PE locations to better optimize the load logic for semi-auto inducts</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> 10/17 - load logic was adjusted... monitor PE response.
|
||
KK 10/27 - This is a duplicate item related to bulk induct shutes (row 6), I will close it</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam Cam visibility in SCADA</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Autstand needs to set up passwords/remove pw for it to work in the scada</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> complete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Chute 14041 Enable Issues</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> DTC chute won't stay enabled even with cart in correct position and button pressed</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">VS-D, S01400 Pallet Chute Beacons - False Fullness</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Chute fullness indicator beacon illuminated incorrectly, check all chutes but specifically S014020, S014018</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/15</p>
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi-Auto Jam Beacons</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> remove jam PE at chute</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-28</p>
|
||
<p><strong>Status Updates:</strong> 10/19 PE functionality diabled.. hardware removal to be scheduled TBD
|
||
KK 11/4 - hareware was removed on 10/28</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NC Dim Data</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> AutStand not sending DIM data in S01 Message</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/15 - Matt Specht fix mid sort
|
||
10/17 - COMPLETE</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam Reset NC End of Sorter</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Need to add jam reset pb for end of sorter jam pe, currently the only reset is at the head of the nc sorter</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> duplicate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS11_11_JR3</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Jam Reset PB is flashing sporadically</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> 10/17 - in process
|
||
10/18 KK - Done</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">"Destination Not Attempted" Reason Code</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Receiving "Destination Not Attempted" in the wrong use case/scenario for the NC Sorter, see screenshot</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-21</p>
|
||
<p><strong>Status Updates:</strong> 10/17 -- follow up
|
||
KK 10/21 - Based on container research data from Sherri, this reason code is no longer being sent in our S04</p>
|
||
<p><strong>Image:</strong> image.png</p>
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">S013089 Blue Beacon</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Need to investigate ZMX Sensor, alignment causing false fullness indication</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Done, beacon replaced</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS lines stop packages at the top of the line, on the first station. It should push the packages to the last station Jackpot probem solve</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> 10/17 fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Still seeing Lost Container / No Reads in NC Jackpot</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> 10/16- Reviewed logic/flow. Updated installed at noon. Will be monitoring
|
||
KK 10/27 - Issue seems to be resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">First chute orange lights keeps turning on without pakages blocking any sensors semi auto vs-d</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> Fixed, realigned PE</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Flashing and steady blue light on a chute without any package present S014020, S014018</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> Please ensure the cart is loaded centered in the chute, too far to the left or right, or skewed will result in the overhead sensor will read the frame of the cart and prematurely trigger full
|
||
10/17 - fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Flashing Green light on D2C , start button doesn't work S014041</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> Fixed - bad button, has been replaced</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">non- con packages still has divert issues packages going straight to jackpot</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> Temporary buttons in placed at the end of each sorter, brackets pending</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Scada Map not showing cameras</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> SCADA is showing cameras, the live feeds don't work at the moment, pending AMZ response for configuration (I contacted Davo and JC from ops eng for this)
|
||
10/17 fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Scada Map: showing stopped but actually running C</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> 10/17 - need more info
|
||
KK 10/18 - Need more info
|
||
KK 10/21 - No clarification received
|
||
KK 10/27 - No clarification received, closing this item</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS lines stop packages at the top of the line, on the first station. It should push the packages to the last station.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> Fixed - corrected flow control on problem solve rollers</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Still seeing Lost Container / No Reads in NC Jackpot as of 1044</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> Flow/assignment issue - to be addressed by Sherri (AMZ) and MFO today 11/1
|
||
10/17 monitor
|
||
KK 10/27 - Issue seems to be resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">206 - 207 max reach giving us false signals its green on skada but not operational</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> Need further clarification 10/19 - completed
|
||
10/19 KK - Done</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NC boxes are diverting to xbelt causing jams particullary at bypass curves</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> 10/17 - Ian adjusted the 3 merges on MCM2 to max length to xbelt to 42" Monitor and update MCM01 flow splitter</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Noncon detection length reduced to 41"</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Bypasses are "going to sleep"</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> 10/17 - there is no sleep or energy mgt on the bypasses Will die back if induct is not running</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Take away line from shuttle tipper side pan is loose and causing jams/PE mis alignment</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> 10/17 DCS investigated and found the PEs on one of the tipper takeaways was installed/attached incorrectly. Autstand was advised to fix PEs</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> KK 10/27 - Investigated, found no issues</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Packages not diverting on the correct intralox</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Need further clarification
|
||
KK 10/21 - No clarification received - closed as duplicate (Row 120)</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Label auto inducts</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-20</p>
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">False blue lights</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S014020 (AUTO-CHUTE4020) , S014018 (AUTO-CHUTE4018)</p>
|
||
<p><strong>Date Identified:</strong> 10/25/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> duplicate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">S012075 unavailable</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S012075</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> KK 10/19 - Done</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">VSD- S014020 BLINKING BLUE WHILE CHUTE IS EMPTY</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Virtual sort- D</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> IH 10/18 - Confirmed functionality of the chute.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">VSD- S014018 SOLID BLUE WHILE CHUTE IS EMPTY</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Virtual sort- D</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> IH 10/18 - Confirmed functionality of the chute.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">D2C S014041 flashing green + activation button not illuminating</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Virtual sort D D2C S014041</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Problem Solve rollers do not correctly inch-and-store packages, causing line to jam prematurely</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/17 - PRS photoeyes have been re-aligned and tightened</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA: We need some type of refrence in SCADA. Suggest adding dock doors that correlate with their belt</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Flow Desk</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-07</p>
|
||
<p><strong>Status Updates:</strong> KK 11/7 - Added dock door numbers to screens</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA: Need a way to click onto jammed area on main page to see where the jam is located and how to get there</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Flow Desk</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 - That exists. Sherri showed several team members an dRME how to do this</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Run-up is not enabled on Problem solve collection belts. They all stop when the photoeye at the rollers is blocked.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Problem solve</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/17 - PRS photoeyes have been re-aligned and tightened</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Potential PE issue at the problem solve rollers right when the chutes level off. 300 side.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> BC problem solve</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/17 - PRS photoeyes have been re-aligned and tightened</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA: scada camera view from main map wont allow user to pan camera angles when clicked onto</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Flow Desk</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Adjusting the camera angle is not possible from SCADA. Can be done by accessing the camera directly with its IP address.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS9-3CH2 - located by semi induct C. Blue light actived with no packages</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Semi induct C</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> MC: Blue Light was NOT on when investigated, still went ahead to realign better PE/teach again (10/18/25)</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">semi induct c chute 2 Flase blue light PE needs adjusted</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> MC: Blue Light was NOT on when investigated, still went ahead to realign better PE/teach again (10/18/25)</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non con diverts going down - becon alluminating but belt still running</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> interlock</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Need clarification
|
||
KK 10/19 - Closed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">IBNC splitting sending packages to NC that are within the crossbelt MTBH</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Inbound</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-16</p>
|
||
<p><strong>Status Updates:</strong> KK 10/16 - Splitter logic adjusted</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">D2C Chutes are full blue lighting 8 inches short of the go cart full line</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> VS-D (But I assume all virtual sorters)</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-16</p>
|
||
<p><strong>Status Updates:</strong> KK 10/16 - Raised ALL D2C Full height 6-8" above last setting</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">chute stays green even when chute is full</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Chute S014073</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> IH 10/18 Resolved. IO Mapping issue.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non- con packages coming down to lanes</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> VS-D</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Noncon detection length reduced to 41"</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Scada - label each line ex. UL13 , UL14 ect.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Inbound 3-1 merges</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> IH 10/19 SCADA Updated</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS11-11CH6NC Intralox Sorter (S02)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> PS11-11CH6NC Intralox Sorter (S02)</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/27 - Need clarification. I don't see the relation between PS11-11 and the intralox sorter.
|
||
KK 11/10 - Did not receive clarification, closing this item</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Blue light for semi induct D is on when chute is empty</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> PS11-11CH6NC</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Realigned and trained photoeye</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Need 1 button to turn on ALL inducts. I am having to turn them on one by one</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Buemer scada</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Our global start button is confirmed to start all autStand conveyors and Beumer CMC/SMC conveyors, only if they are not faulted.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non-Con running through main sorter causing system to shutdown; Non-con packages not diverting to Non-cons sorter taking up carriers on Sorter</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Main Sorter</p>
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Noncon detection length reduced to 41"</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">DTW8/CLE5 Non-Con packages not diverting to chutes; running straight through jackpot</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non-Con sorter</p>
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - MFO issue
|
||
KK 10/19 - Not MFO, need to deep dive tracking/diverting/etc
|
||
KK 10/20 - Identified potential issue with a photoeye missing incoming packages at scan tunnel induct, which manifest as unknown/unexpected packages and causing some packages to go off-the-end. We adjusted this sensor and are monitoring. Initial observations seem promising
|
||
KK 10/27 - Resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SEMI-D uneven flow of packages to each chute</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> SEMI-D</p>
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Logic continually being optmized (monitor)
|
||
KK 10/27 - This is a duplicate item related to bulk induct shutes (row 6), I will close it</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Clean up SCADA Active Jams to not show false jams ex BYBA-15 /BYBD-14</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/21 - Aware of a couple "stuck" alarms - still investigating why RS 10/30 - This issue seems to be fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Disable jam pe's that are to be removed (bulk chutes)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Disabled, pending physical removal</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Evaluate jam logic /die back on bypasses.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> getting "false jams" of box stopped in from of PE when belt stops. Bypass jams are difficult to access need to minimize them</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-19</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> KK 10/19 - Verified that it is not being caused by runup logic, need to continue to monitor
|
||
KK 10/27 - False jams seemed to have stopped being as frequent. There is still no runup logic causing this.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non Con flow issues -- missorts to S02207</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-27</p>
|
||
<p><strong>Status Updates:</strong> KK 10/27 - Resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA performance issue</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> report export crashed system</p>
|
||
|
||
<p><strong>Date Completed:</strong> 2025-11-04</p>
|
||
<p><strong>Status Updates:</strong> 11/1 RC - SCADA was updated to improve performance yesterday NIGHT.
|
||
KK 11/4 - Assuming this is related to SCADA crashing when trying to export large amounts of data (like a week of alarms). We addressed, just tested and it did not crash.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">3:1 merge code update</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> mcm02 by monday 11/4. mcm01 ul 1-3 done. mcm01 complete.</p>
|
||
|
||
<p><strong>Date Completed:</strong> 2025-11-09</p>
|
||
<p><strong>Status Updates:</strong> 11/3 - no update... Igor at BNA8
|
||
KK 11/6 - Plan sent to AMZ, targetting to execute at noon on 11/8
|
||
KK 11/8 - Lack of downtime today prevented us from executing, we are replanning for tomorrow 6-8AM downtime, operations put a building volume cap in place
|
||
KK 11/10 - This was complete yesterday, marking as Complete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">gap control at non con sorter.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> code change/ help with box tracking.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-30</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-04</p>
|
||
<p><strong>Status Updates:</strong> working on it today. /tomorrow
|
||
KK 11/4 - 0 gap errors since logic update, closing this item</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Raise the fill height ob the DTC's approx 2 "</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-11-04</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-05</p>
|
||
<p><strong>Status Updates:</strong> RC 11/6 - All DTC chutes' full heights have been raised 6".</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS8-5 Jammed but not showing on SCADA</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> KK 11/6 - Per Chris' Twi sort 11.6 report - PS8-5 jammed but did not animate on SCADA</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-06</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/12 - Fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NCP1-6-TPE1 did not alarm correctly on SCADA when jammed</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Jiffy got to noncon and stuck in a T-plate causing NCP1-6-TPE1 to jam, but this did not animate at all on SCADA, leading to a slower than typical resolution (KK 11/7)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> RC 11/8 - Incorrectly in what way?
|
||
KK 11/8 - Fixed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Over-width noncons diverting to crossbelt</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Packages that are over-width that should pass through to noncon are being diverted at the inbound flow splitter - causing jams (KK 11/7)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-09</p>
|
||
<p><strong>Status Updates:</strong> KK 11/7 - We are investigating how to add width into the divert decision at inbound.
|
||
|
||
KK 11/8 - Robin made the hardware/software updates to PS1/2/3, will continue the rest tomorrow
|
||
|
||
KK 11/10 - Over-width detection has been added to all PS lines as of last night</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Aligner vertical belts running when rollers are jammed</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Dead rollers on one of the aligners caused the aligners to jam and stop running, but the vertical belt kept running - damaging the vertical belt</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-10</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-10</p>
|
||
<p><strong>Status Updates:</strong> KK 11/10 - I modified the logic to work this way. If downstream is running, that allows the rollers to run. If the rollers are running, then the vertical belt is allowed to run. Previously, if downstream was running, both the rollers and vertical belt were allowed to run.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Noncons being diverted to PS lines</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Noncons are being diverted to PS lanes. Happens sporadically, not systemically. Seems to occur primarily at PS2, with some reports of it happening at PS7. (KK 11/10 - this has been occurring but never formally logged)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-10</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/10 - Still unsure why this happening. Hard to evaluate whether any potential fixes we apply are effective without data. Most occurences come anecdotally and with pictures. We can observe PS2 splitter for 30 mins and watch dozens of noncons pass through correctly. Igor and Robin are both still actively investigating the issue.
|
||
|
||
KK 11/11 - Duplicate now that Amazon updated this list with their internal punchlist. Row 199. Closing this one.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Fluid Load Lane displays as "Lane Unavailable" when the FLL is actually operational (blue lit).</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Fluid Load Lane displays as "Lane Unavailable" when the FLL is actually operational (blue lit).</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-09</p>
|
||
<p><strong>Status Updates:</strong> 11/07 - D99 - messages are not correct. Reporting lane unavilable. Beumer needs to update messages.
|
||
11/6 Past due. Logic changes were attempted yesterday but didn't work and were rolled back. Now testing on one lane (BYCD 2). Autstand (integrator) is making code changes with internal controls team monitoring. Results expected tomorrow.
|
||
11/5 due to the SEV2 on NIT sort 11/4, site would like to monitor for one more day.
|
||
11/4 Implemented logic change 11/4 - monitoring.through 11/5 and will be closed if no new issues are reported.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Bypass shows as Lane Unavailable/Non-operational when the Bypass is at capacity (full/blue lit).</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Bypass shows as Lane Unavailable/Non-operational when the Bypass is at capacity (full/blue lit).</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-09</p>
|
||
<p><strong>Status Updates:</strong> 11/07 - D99 messages need to be updated. Beumer needs to update the messages.
|
||
11/6 Similar to MTN6-002, bypass lines being optimized with inch in store logic to maintain product flow and reduce lane unavailables. Testing in progress
|
||
11/5 Testing the run up logic was not successful, @davaoste is waiting for next steps from the vendor.
|
||
11/4 Bypass Logic will be updated on one sorter to test - if successful, the defect will now show as lane full instead of Lane unavailable and will roll out to the rest of the bypasses by 11/7 if no issues are found in the test period.
|
||
11/3 Once FLL change has been monitored and confirmed, Logic change will be rolled out to the bypasses. Need to rollout separately to have time to monitor clean data before rolling out the second change.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Merge optimization is underway with the non-con specification temporarily reduced from 47" to 42" while Autstand optimizes the merges. The inducts to Virtual sorters A and C (UL1-12) have been completed. Once all inducts are optimized, the non-con spec will be expanded back to 47". During this optimization process, it's safer to route smaller packages to non-con rather than sending larger packages to the crossbelt system.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Merge optimization is underway with the non-con specification temporarily reduced from 47" to 42" while Autstand optimizes the merges. The inducts to Virtual sorters A and C (UL1-12) have been completed. Once all inducts are optimized, the non-con spec will be expanded back to 47". During this optimization process, it's safer to route smaller packages to non-con rather than sending larger packages to the crossbelt system.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - In progress
|
||
11/07 - Improvement made in flow splitters with proper diverts. However, square boxes are still creating jams. Logic to prevent small boxes going to NC and NC going to XB has been fixed. 11/6 Egor evaluating timing issues with 3-to-1 merge logic. Only first 3 merges updated, 4 remaining need logic updates. Gapping/pitching incomplete on MCM2-1, scheduled for Saturday.
|
||
11/5 Will coordinate with OPS for schedule of DT windows for each IB lane to make the update. Will be completed by 11/7
|
||
11/4 Testing completed,, will rollout 1 IB lane at a time to be completed by 11/5.
|
||
11/3 Logic change to reduce 42" until merge logic optimization is complete.
|
||
KK 11/11 - To be clear, we had to reduce to 42" because the auto induct will reject anything greater than that. It will not be raised back to 47". Discussed on the daily call today - moving to design rather than mechanical/controls.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The panel has a blinking jam indicator active all the time</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The panel has a blinking jam indicator active all the time</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Autstand advised of the observation
|
||
11/09 - Issue logged
|
||
KK 11/11 - This indicator is not blinking as I write this message. Did the person who report this check if there was actually a jam in that system..? I went and checked now and it is off. Closing the item</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="Autstand">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (10)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Replicate logic timers from semi VS-D to the rest of the semis</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Logic timers from semi-auto at all virtual sorters need to be adjusted</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/16 - fix applied monitor as VS become active</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Logic for Semi induct D is off very low throughput see video</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Semi Auto D induct</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Tweaking logic, continually adding optmizations</p>
|
||
<p><strong>Image:</strong> see video in comments</p>
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">One major issue and one minor issue with the non-con system:
|
||
No-reads are really frequent
|
||
The PLC is not reporting S04 message divert fails properly (no reads to jackpot, lost container, failed to divert, wrong buildings)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> NON con sorter 1 and 2 not diverting</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - For the whole sort yesterday we had 13 No Reads out of 500 inducted (2.6%) we will see what can be done to reduce this.
|
||
IH 10/19 Datalogic & PLC update conducted. Will continue to monitor.
|
||
KK 11/30 - Fixed the "Unknown" S04 message, verified with AWCS data</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">DTC chutes on VS-B is randomly disabling</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/30 RC - Is this still an issue? Chute code was updated to add a debounce period for registering a cart removal. This should mitigate any false removals caused by jiffies triggering the sensor while falling into the cart.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Bypass improvements</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Bypass showing lane unavailable when not running, instead of full. Bypass shows relatively high unavailable rate. (KK 11/7 - Writing this descrpition retroactively, I am not sure who began tracking this issue or when)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-03</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/4 - All bypasses were made to show "Full" rather than "Unavailable" when the bypass was not running
|
||
KK 11/5 - Tried enabling run-up for a bypass lane, issue with logic, caused jams, rolled back
|
||
KK 11/7 - Run-up logic enabled on whole BYDC during downtime, will monitor upcoming sort
|
||
KK 11/9 - Run-up for all bypass belts enabled, caught a few cases where there were jams, we fixed the logic.
|
||
KK 11/10 - Almost all bypass jams dropped from the jam hitlist today, a good sign.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Sorter statistics on SCADA</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Add crossbelt sorter statistics to ignition SCADA (KK 11/7 - Writing this descrpition retroactively, I am not sure who began tracking this issue or when)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-03</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/7 - Updated statistics section of SCADA to show sorter stats before 11/7 DAY sort. First time testing with live data, there are some bugs to address
|
||
KK 11/8 - Updated SCADA to address sorter statistic bug, looks correct now, pending validation by Amazon</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Update SCADA to show inch and store status of conveyors with such functionality</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Update SCADA to show inch and store conveyors as YELLOW while inch and store is enabled and BLUE while inch and store is full (KK 11/7)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/9 - Done for all FL lanes and PRS lanes, bulk to follow</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jiffys to noncon</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Jiffys are getting to noncon causing jams and potential damage to intralox sorters (KK 11/7)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/7 - Observed inbound flowsplitter to see why jiffys were not being diverted. Findings were that very light jiffys or jiffys with non-flat topology could not physically be diverted successfully. The tracking PEs and logic worked as it should. The diverting mechanism actuates when the jiffy traversed the divert point.
|
||
|
||
In the case of light jiffys, they other did not have enough weight to engage with the roller bed to divert, or they started to divert but catch air which then reduces downward pressure and reduces engagement with divert mechanism.
|
||
|
||
In the case of non-flat jiffy (convex or circular footprint), the jiffy tumbled or rolled around when trying to divert.
|
||
|
||
In both cases, we grabbed several jiffys that failed to divert due to physics and re-inducted them, to prove that the logic was picking them up and attempting to divert them, and in some cases they were diverted.
|
||
|
||
I have reached out to DCS and intralox to confirm what the minimum recommended MTBH weight is for the inbound intralox flow splitters.
|
||
|
||
KK 11/8 - Talked with Deepak about potential solutions, he suggest having a fixed divert on each noncon sorter and divert anything less than noncon length there (including jiffys). He said he would follow up internally and let us know how to proceed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS8-6 flow splitter eating packages</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> PS8-6 flow splitter is sucking in packages at the discharge end (KK 11/7)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/8 - Observed this for about 2 hours during TWI sort. I saw the scenario that could lead to a package getting sucked in. 50% physics and 50% logic. Very light jiffys tend to ignore the divert rollers, just like inbound. I modified the PS8-5 splitter logic and PS8-8 flow logic in order to mitigate this happening. Ultimately I think it is not 100% preventable, except for maybe waterfalling onto the conveyor directly</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Run up logic needs to be activated all across the site. When a conveyor stops their signal drops for all the conveyor behind creating unnecessary start stop and not allowing for accumulation.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Run up logic needs to be activated all across the site. When a conveyor stops their signal drops for all the conveyor behind creating unnecessary start stop and not allowing for accumulation.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/09 - attached video for reference. Run up logic needs to be enabled on all conveyors to allow packages to accumulate without creating a lot of empty space impacting throughput. When the inducts start the system should be able to keep up with induct rates. The video also shows a regular package trying to divert.
|
||
|
||
KK 11/12 - Runup was enabled in MCM03, so that when the NC sorter is down, noncon packages can continue past the inbound flow splitters and queue up as. This should help inbound run longer when noncon goes down. Any other runup areas need to be discussed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="Autstand">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (14)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Encoder failure (4x) + 2 x</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> UL8-7 UL11-7 Problem with port on APF</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-10</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/23 ST soluton is changing the port... LT reseach with Rockwell 10/29 - Rockwell to send engineer to test system 10/30 ; 10/30 RC - Rockwell visit not happening today. TBD. 10/30 - looking to send "capable engineer" to address engineer. today another encoder failed UL18-10 (all merge stop - 20 min swapping) 11/3- Rockwell scheduled to be on site 11/6.
|
||
|
||
KK 11/7 - Rockwell came to site and investigated, but ultimately was not able to deterine the root cause of the issue, they collected data which they will use at their lab to try to recreate the issue and investigate further.
|
||
|
||
KK 11/8 - Rockwell suggested to try a different setting on the encoders, we are targetting 11/10 to do this.
|
||
|
||
KK 11/10 - Not enough downtime during the day to do the change
|
||
|
||
KK 11/12 - We are doing the suggested change on UL14 during the DAY/TWI downtime window. Will evaluate for the next sort.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">7:1 merge code update</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/10 - Will not happen before peak</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Estops are getting damaged on the UL lane</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> UL16-1, UL15-3, UL10-2 (both sides) UL8-1 , UL7-3, UL6-1 protect or relocate devices</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-04</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/10</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Fix tippers faulting mid-dump sequence</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Tippers that are flow-stopped during the dumping sequence will remain raised and fault after a period of inactivity.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-06</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/7 - It seems this only started happening once the code from Pioneer was "updated". Requires further investigation - as holding a tipper queued up and ready to tip as soon as the belt became available has always been standard practice.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PE not showing on scada/beacon</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Level (50/100% fullness) PEs are not showing in SCADA or in the beacons — tested on chutes DD119, DD319, DD320, and DD321 — which indicates a system issue affecting both SCADA and the beacon network.
|
||
|
||
There are also instances where SCADA displays blue (package detected) while the beacon does not, even though no package is physically present, suggesting inconsistent signal behavior between both systems.
|
||
|
||
Additionally, several PE connectors were found disconnected from the cable box, which could be contributing to the issue.
|
||
|
||
Issue shown to Carlos Radielli.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-10</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/11 - Root cause identified last night, patch to be rolled out today. SCADA server running out of resources, causing it to become unresponsive and show the wrong statuses. Scada 2.0 template bloat and ineffecient data/alarm handling on our end will be addressed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA is being updated through cooperation between Autstand and Firm Engineering across all three Autstand sites (SAT9, MTN6, CNO8). Operations has identified Active Alarms as a barrier, as the alarms are backlogged and not clearing from the Active Alarms tab. Additionally, the Statistics/Status tab is currently unavailable, limiting system monitoring capabilities.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> SCADA is being updated through cooperation between Autstand and Firm Engineering across all three Autstand sites (SAT9, MTN6, CNO8). Operations has identified Active Alarms as a barrier, as the alarms are backlogged and not clearing from the Active Alarms tab. Additionally, the Statistics/Status tab is currently unavailable, limiting system monitoring capabilities.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Monoriting
|
||
11/7 - Autstand pushed updates for sorter statistics. Needs validation before closing this item.
|
||
11/4 @deepak requested a list of the Metrics that are needed and currently not available. Expo will be onsite 11/7 and will compile a list.
|
||
11/3 Austand working through update improving user interface.
|
||
|
||
KK 11/11 - Root cause identified last night, patch to be rolled out today. SCADA server running out of resources, causing it to become unresponsive and show the wrong statuses. Scada 2.0 template bloat and ineffecient data/alarm handling on our end will be addressed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Punch holes on bypass photo eyes are damaging packages</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Punch holes on bypass photo eyes are damaging packages</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/07 - Punch holes on bypass were reviewed and pictures taken. Work in progress
|
||
KK 11/11 - Nerio on site will evaluate, seems to be an issue mostly around curves and long packages.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The 3 to 1 merge is merging side by side creating jams downstream. This could also lead to double packages getting inducted to the sorter.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The 3 to 1 merge is merging side by side creating jams downstream. This could also lead to double packages getting inducted to the sorter.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-08</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/8 - issue added from Controls deep diving on site. Vendor has updated the merge logic using a MCM. Issue to be monitored. Video attached.
|
||
|
||
KK 11/11 - There is no systemic issue that we are aware of. There are two specific belts, one on UL9 and UL14 that under certain circumstances can cause a side-by-side because they are behaving errantly. These two belts do not stop or start at the speed which we need for the logic to work. We have already tried swapping the VFD and brake resistor, and verified the logic. We discussed with DCS and they assured us that it could not be a mechanical issue.
|
||
|
||
We have seen every day packages being unloaded side-by-side directly from the trailer, and packages loaded on top of eachother. Frankly, I think most of the side-by-sides are caused by this. Not to say that we have occurences due to the merge, but it is not the only factor.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non-con packages are getting diverted to auto induct causing jams at the inducts and too many reversals by the auto induct.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non-con packages are getting diverted to auto induct causing jams at the inducts and too many reversals by the auto induct.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-08</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10- Autstand added logic to measure width in addition to length to identify packages that may have rotated orientation.
|
||
`1/09 - deep dive from controls shows measurements are not reliable and lengths are not calculated accurately causing in-consistent behavior at the flow splitter.
|
||
|
||
KK 11/10 - Still unsure why this happening. Hard to evaluate whether any potential fixes we apply are effective without data. Most occurences come anecdotally and with pictures. We can observe PS2 splitter for 30 mins and watch dozens of noncons pass through correctly. Igor and Robin are both still actively investigating the issue.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam beacons at the merge are not showing jams. It is happening across all merges.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Jam beacons at the merge are not showing jams. It is happening across all merges.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-08</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Autstand adjusted the PE- monitoring , 11/09 - After further inspection all the jam beacons are reporting the wrong place. Jam happened at the 7-1 merge, the beacon light up but jam cannot be found in that location.picture attached for reference.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">When conveyor are starting they start all at ones and that also contributes to a start stop behavior. A cascade start is suggested</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> When conveyor are starting they start all at ones and that also contributes to a start stop behavior. A cascade start is suggested</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/09 - cascade logic will allow the system not having continuous start stop behavior. Currently there is no cascade start sequence on the conveyors. By adding cascade delay while starting up the system can minimize the number of start and stops.
|
||
|
||
KK 11/12 - Need clarification on what exactly the ask here is</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non con package to jackppt</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Packages going directly to jackpot, jam the sorter and affect overall flow</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-11</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/11 - Issue first occurred last night at the end of DAY sort. Igor cam and investigated, noticed high number of unexpected package and lost tracking. Identified some problem PEs and adjusted.
|
||
|
||
The issue occurred again at the beginning of DAY sort 11/11. Igor came in and is still investigating. The issue is transient.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA issues see SCADA Tab</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Validating SCADA accuracy</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-11</p>
|
||
|
||
<p><strong>Status Updates:</strong> Outlining SCADA discrepencies on week of 11/10.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">S013064 – Blue indicator light remained active without packages present, suggesting a possible sensor or control fault; RME was called to investigate issue.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S013064 – Blue indicator light remained active without packages present, suggesting a possible sensor or control fault; RME was called to investigate issue. (Taken from operations report for 11/11 MOR sort - KK 11/12)</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-11</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 11/12 - This was reported to us on 11/12</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="Autstand/Beumer">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">Autstand/Beumer</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">5</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">3</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">2</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'Autstand/Beumer')" data-status="all">All (5)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand/Beumer')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand/Beumer')" data-status="oldest_unaddressed">Oldest Unaddressed (2)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand/Beumer')" data-status="closed">Closed (3)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand/Beumer')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand/Beumer')" data-status="incomplete">Incomplete (2)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="Autstand/Beumer">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Critical Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">It's been observed that BG Fusion and HMI systems don't match when displaying sorter health status. On multiple occasions, when a chute or lane shows as blue lit on BG Fusion, it doesn't appear on the HMI and vice versa, creating confusion about actual system status.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> It's been observed that BG Fusion and HMI systems don't match when displaying sorter health status. On multiple occasions, when a chute or lane shows as blue lit on BG Fusion, it doesn't appear on the HMI and vice versa, creating confusion about actual system status.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Being audited by on site team and actioned
|
||
11/7 - Autstand requires a data sync when Beumer makes any changes. This still needs to be validated 11/5 Awaiting deep dive update from FE Controls.
|
||
|
||
KK 11/11 - Root cause identified last night, patch to be rolled out today. SCADA server running out of resources, causing it to become unresponsive and show the wrong statuses. Scada 2.0 template bloat and ineffecient data/alarm handling on our end will be addressed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">There is many items that bg fussion has that doesn't match the SCADA provided by the vendor. Auto induct jams not showing is one example</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> There is many items that bg fussion has that doesn't match the SCADA provided by the vendor. Auto induct jams not showing is one example</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/09 - Issue Logged
|
||
|
||
KK 11/11 - Root cause identified last night, patch to be rolled out today. SCADA server running out of resources, causing it to become unresponsive and show the wrong statuses. Scada 2.0 template bloat and ineffecient data/alarm handling on our end will be addressed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">Other Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">pe missing prob solve ak chute</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-29</p>
|
||
|
||
<p><strong>Status Updates:</strong> Completed 10/29</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">No Priority (2 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi induct D - light not allumintating green</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Need further clarification
|
||
KK 10/19 - Done</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Bypasses are showing "lane unavailble" at a high rate. should always be available... is it in energy saving mode? or other reason</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-04</p>
|
||
<p><strong>Status Updates:</strong> 10/30 RC - AutStand removed rate management logic that caused Conveyor Not Ready status in SCADA. AutStand to monitor whether bypass jams increase. Beumer to adjust to-bypass discharge rate if necessary. 11/06 RC - Bypass and FL lanes now report "full" instead of "not available".</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="Autstand/Beumer">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="Autstand/Beumer">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items (2)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">It's been observed that BG Fusion and HMI systems don't match when displaying sorter health status. On multiple occasions, when a chute or lane shows as blue lit on BG Fusion, it doesn't appear on the HMI and vice versa, creating confusion about actual system status.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
<span class="age-days">6 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> It's been observed that BG Fusion and HMI systems don't match when displaying sorter health status. On multiple occasions, when a chute or lane shows as blue lit on BG Fusion, it doesn't appear on the HMI and vice versa, creating confusion about actual system status.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Being audited by on site team and actioned
|
||
11/7 - Autstand requires a data sync when Beumer makes any changes. This still needs to be validated 11/5 Awaiting deep dive update from FE Controls.
|
||
|
||
KK 11/11 - Root cause identified last night, patch to be rolled out today. SCADA server running out of resources, causing it to become unresponsive and show the wrong statuses. Scada 2.0 template bloat and ineffecient data/alarm handling on our end will be addressed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">There is many items that bg fussion has that doesn't match the SCADA provided by the vendor. Auto induct jams not showing is one example</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
<span class="age-days">4 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> There is many items that bg fussion has that doesn't match the SCADA provided by the vendor. Auto induct jams not showing is one example</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/09 - Issue Logged
|
||
|
||
KK 11/11 - Root cause identified last night, patch to be rolled out today. SCADA server running out of resources, causing it to become unresponsive and show the wrong statuses. Scada 2.0 template bloat and ineffecient data/alarm handling on our end will be addressed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="Autstand/Beumer">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (3)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi induct D - light not allumintating green</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Need further clarification
|
||
KK 10/19 - Done</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Bypasses are showing "lane unavailble" at a high rate. should always be available... is it in energy saving mode? or other reason</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-04</p>
|
||
<p><strong>Status Updates:</strong> 10/30 RC - AutStand removed rate management logic that caused Conveyor Not Ready status in SCADA. AutStand to monitor whether bypass jams increase. Beumer to adjust to-bypass discharge rate if necessary. 11/06 RC - Bypass and FL lanes now report "full" instead of "not available".</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">pe missing prob solve ak chute</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-29</p>
|
||
|
||
<p><strong>Status Updates:</strong> Completed 10/29</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="Autstand/Beumer">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="Autstand/Beumer">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (2)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">It's been observed that BG Fusion and HMI systems don't match when displaying sorter health status. On multiple occasions, when a chute or lane shows as blue lit on BG Fusion, it doesn't appear on the HMI and vice versa, creating confusion about actual system status.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> It's been observed that BG Fusion and HMI systems don't match when displaying sorter health status. On multiple occasions, when a chute or lane shows as blue lit on BG Fusion, it doesn't appear on the HMI and vice versa, creating confusion about actual system status.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Being audited by on site team and actioned
|
||
11/7 - Autstand requires a data sync when Beumer makes any changes. This still needs to be validated 11/5 Awaiting deep dive update from FE Controls.
|
||
|
||
KK 11/11 - Root cause identified last night, patch to be rolled out today. SCADA server running out of resources, causing it to become unresponsive and show the wrong statuses. Scada 2.0 template bloat and ineffecient data/alarm handling on our end will be addressed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">There is many items that bg fussion has that doesn't match the SCADA provided by the vendor. Auto induct jams not showing is one example</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> There is many items that bg fussion has that doesn't match the SCADA provided by the vendor. Auto induct jams not showing is one example</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/09 - Issue Logged
|
||
|
||
KK 11/11 - Root cause identified last night, patch to be rolled out today. SCADA server running out of resources, causing it to become unresponsive and show the wrong statuses. Scada 2.0 template bloat and ineffecient data/alarm handling on our end will be addressed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="Autstand/DCS">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">Autstand/DCS</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">5</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">5</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'Autstand/DCS')" data-status="all">All (5)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand/DCS')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand/DCS')" data-status="oldest_unaddressed">Oldest Unaddressed (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand/DCS')" data-status="closed">Closed (5)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand/DCS')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Autstand/DCS')" data-status="incomplete">Incomplete (0)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="Autstand/DCS">
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (2 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Flow splitters are rotating boxes, potentially contributing to jams. Timing and height of the pop up rollers need to be evaluated</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> 10/17- Autstand and DCS to evaluate and make adjustmets</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> IH 10/18 Updates made to flow splitter logic to refine the window of the "pop-up rollers"</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The vertical belts on the aligner unit runs while the aligner unit has stopped on a jam. This is causing the packages to rotate and create package damage.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The vertical belts on the aligner unit runs while the aligner unit has stopped on a jam. This is causing the packages to rotate and create package damage.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-10</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - This issue was brought up on the MTN6 vendor call. The vertical belt should not run when the aligner unit has stopped running. Vendor completed the logic update. Amazon to validate
|
||
KK 11/11 - Added the logic to prevent this from happening.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">Other Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jiffies and small packages incorrectly routing to non-con area</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Jiffies and small packages incorrectly routing to non-con area</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-06</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-11</p>
|
||
<p><strong>Status Updates:</strong> 11/10 - part of NC routing work stream above
|
||
11/09 - deep dive from controls shows measurements are not reliable and lengths are not calculated accurately causing in-consistent behavior at the flow splitter. video attached of smalls packages traveling to non-con.
|
||
11/07 - Logic to prevent small boxes going to NC and NC going to XB has been fixed. 11/6 Egor from Autstand conducting the initial DD.
|
||
KK 11/11 - This is a duplicate. See row 175. I will close this one.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">No Priority (2 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS collector photo eyes are not feeding into each other</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> PS collector photo eyes - both collectors</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/17 - PRS photoeyes have been re-aligned and tightened</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non-con packages with plastic securement strips are not to be ran on sorter. Packages with plastic securement strips gets caught in sorter causing it to shut down/ jam.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non-Con sorter</p>
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Our system can not tell if a package has plastic securement strips</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="Autstand/DCS">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="Autstand/DCS">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No unaddressed items</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="Autstand/DCS">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (5)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Flow splitters are rotating boxes, potentially contributing to jams. Timing and height of the pop up rollers need to be evaluated</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> 10/17- Autstand and DCS to evaluate and make adjustmets</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> IH 10/18 Updates made to flow splitter logic to refine the window of the "pop-up rollers"</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS collector photo eyes are not feeding into each other</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> PS collector photo eyes - both collectors</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/17 - PRS photoeyes have been re-aligned and tightened</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non-con packages with plastic securement strips are not to be ran on sorter. Packages with plastic securement strips gets caught in sorter causing it to shut down/ jam.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non-Con sorter</p>
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Our system can not tell if a package has plastic securement strips</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jiffies and small packages incorrectly routing to non-con area</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Jiffies and small packages incorrectly routing to non-con area</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-06</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-11</p>
|
||
<p><strong>Status Updates:</strong> 11/10 - part of NC routing work stream above
|
||
11/09 - deep dive from controls shows measurements are not reliable and lengths are not calculated accurately causing in-consistent behavior at the flow splitter. video attached of smalls packages traveling to non-con.
|
||
11/07 - Logic to prevent small boxes going to NC and NC going to XB has been fixed. 11/6 Egor from Autstand conducting the initial DD.
|
||
KK 11/11 - This is a duplicate. See row 175. I will close this one.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The vertical belts on the aligner unit runs while the aligner unit has stopped on a jam. This is causing the packages to rotate and create package damage.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The vertical belts on the aligner unit runs while the aligner unit has stopped on a jam. This is causing the packages to rotate and create package damage.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-10</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - This issue was brought up on the MTN6 vendor call. The vertical belt should not run when the aligner unit has stopped running. Vendor completed the logic update. Amazon to validate
|
||
KK 11/11 - Added the logic to prevent this from happening.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="Autstand/DCS">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="Autstand/DCS">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No incomplete items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="Beumer">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">Beumer</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">36</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">12</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">6</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">18</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'Beumer')" data-status="all">All (36)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Beumer')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Beumer')" data-status="oldest_unaddressed">Oldest Unaddressed (3)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Beumer')" data-status="closed">Closed (12)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Beumer')" data-status="monitor">Monitor (6)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Beumer')" data-status="incomplete">Incomplete (18)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="Beumer">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Critical Priority (8 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Inductions are going directly on bellowsco</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Experiencing too many items on bellow... causing sorter to stop</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Carrier disabled to shut down the sorter</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Sorter shutting down too often</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
<p><strong>Status Updates:</strong> 30% disable threshold... confirm reenable</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Packages are being inducted on occupied trays</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Causing missorts and DBS/IBS/IOB faults that stop the sorter</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/23 - Beumer updated PLC to prevent issue but did nto work. Additional logs were addeed to trace root cause of issue (10/24 @730am)</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Bypasses Not On Due to Auto-Induct Status</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Bypasses were turned off several times during testing</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> 10/14 - Bryan to update code tomorrow
|
||
10/15 - Bypasses had to be manually turned on when crossbelt stopped
|
||
10/16 - Fix applied, monitor</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Missorts</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> File with missorts shared.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-20</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/3 -- Missorts issue with chute trigger settings identified. All chutes evaluated and fixed on 10/30 will evaluate improvements with next Ops report</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Lane Not Available Metric too high</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
<p><strong>Status Updates:</strong> 11/3 - Working with Autstand conveyor ready flag as disabled ... will be addressed by full lane signal (fluidload only). Still need to do similar fix on bypass but need to evaluate when to trigger full lane (vs lane not available0</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">After a jam happens and it is reversed by the autoinduct. This requires human intervention to be reseted. The jam remains ready to be reset but doesnt provide any indication in SCADA so no one know it needs to be reset. Can we just autostart after a jam?</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> After a jam happens and it is reversed by the autoinduct. This requires human intervention to be reseted. The jam remains ready to be reset but doesnt provide any indication in SCADA so no one know it needs to be reset. Can we just autostart after a jam?</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/09 - Beumer is looking in to this. downtime is required to make changes for this.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Induct Jams</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Daily multiple jams on inducts / finger gaurds dislodged resulting in down time</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-11</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (13 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi-Auto Package marking X's</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Remark induct point X's on conveyance in permanent material (paint, ink, tape, etc.)</p>
|
||
<p><strong>Date Identified:</strong> 10/6/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - Beumer to start painting after sort tonight at VS-D
|
||
VS B C A complete... VS-d ECD 10/17 night
|
||
|
||
10/18 confirm if compete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA Accurate Status Reads</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Beumer not sending full accurate lane status to AutStand for SCADA visualization. Beumer needs to send an updated Excel file for AutStand to update.</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/14/2025</p>
|
||
<p><strong>Status Updates:</strong> 10/14 - Autstand now has all of the program info from Beumer to connect statuses
|
||
10/17 resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Auto-Induct Restart</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> After an E-Stop and Restart, Auto-Induction didn't go through its auto clear cycle automatically, someone had to go to the local induction control station</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> 10/17 -- related to the global start? montor
|
||
confirmed that it works</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">False Jam ( Rest every 6 mins)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S013018</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Reassigned to Beumer</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Estop not reporting on BGFusion/Scada</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Sorter stopped could not find root cause. Estop was triggered and not communicated</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-21</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Induct 5B (Bypass induct C->) rejecting packages within MTBH</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> IND5B-5 (Induct platform VSB)</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - will verify Will check calibration, waiting on tool</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Auto induct - D back fireing packages that can go - also demissionier is off</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Auto induct - 7d</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 will investigate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Packages are being directed to the wrong end of the chutes, AA had to take jiffy and scan to D2C</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Chute S014072</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 will investigate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">BUEMER scada - bypass is showing "die back" in yellow and futher up the belt is showing green. There is a disconnect. Packages arent able to move through in "die back" mode but the belt after is showing green, which looks to be good but isnt</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Bypass DA</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - will investigate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">false jam</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Lane S014024</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/19 - Reassigned to beumer, they control crossbelt chute jams</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">DBS sensors - heavier packages meeting weight requirement for main sorter triggering senors; causing sorter to shutdown</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Main Sorter</p>
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - need update for ops on how DBS works</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">jiffies getting caught in belows causing sorter to shutdown</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Cells on Main sorter</p>
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">At inducts evaluate why "conveyable" boxes are being rejected at induction</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Is aligner working as expected? Skewed boxes triggering as oversized</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-19</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">Low Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Throughput Limit on SCADA</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Throughput Limit is being identified on SCADA and Grafana as an error code, despite not being in SFS. Determine root cause of Throughput Limits being triggered and assign them properly.</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 was used for testing is now disabled</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">Other Priority (9 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">VS-D Auto-Induct Jams/Faults</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Training for ops on difference between jams/faults, ops seems to think all faults should clear themselves on auto-inducts, maybe something on minor piece</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - Bryan is working on similar issue at SAT9, Deepak from Amazon is helping, Jody will send people to investigate</p>
|
||
<p><strong>Image:</strong> fixed finger gaurds</p>
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Operations requested the Problem Solve chutes from A and C to be disabled since not staffed</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> 10/17 -- Sherri asked Beumer (Bryan) to disable the 2 chutes from the sorter. Operations to advise when to re-enable</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Air Knife over shooting takeaway conveyor</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Too many packages are falling in netting. Add add'l netting ? refocus air knife?</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-19</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/23 - Airknife out of alignment. Beumer adjusted but requested Silman to return to site to recalibrate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Diverting onto Bellows from Bypass, adjust carrier aim</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Confirm divert points for auto and semi-auto inducts</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - Beumer is going to work on re-aiming some of these auto-inducts, retrain ops on induction angles</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Divert Points to Pallet Chutes</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Confirm divert points to pallet build chutes, light packages were landing in the wrong chutes or stuck in between</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - Check the chutes that have missorts and jams at the top
|
||
10/17 - chutes checked and made adjustments Monitor</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">IND2A-22 Carrier Induct Timing</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Check induct firing direction and timing at IND2A-22, a few packages were observed falling off the carriers being off to the edge</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 - beumer to monitor</p>
|
||
<p><strong>Image:</strong> IMG_4519.jpg</p>
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">auto inducts and inducts need to be restarted manually</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> auto inducts and inducts need to be restarted manually</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 The Induction Global Restart Correction completed . Since then we had a few instances when the safety doors were opened to test the new code. After closing the safety door the sorter started along with the inductions as expected.
|
||
; 11/09 - Issue Logged</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Provide Bellow clearing procedures</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Document the process for clearing bellows for RME</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-17</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Air knife is not firing properly leading to misfires</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Air knife is not firing properly leading to misfires</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Recalibrated but still having issues. Escalating to Beumer ; 11/07 - Camila to connect with Beumer on this issue and update</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">No Priority (5 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">BYPASS ATOC Auto induct reoccuring flase Jam</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Reassigned to Beumer</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Allocations are correct - wrong packages coming down</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S014024 CHUTE</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 will investigate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Deep dive missorts (file shared)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
<p><strong>Status Updates:</strong> Incomplete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Aligner catch point on IND2C-s</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
<p><strong>Status Updates:</strong> Incomplete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Issue with needing to reset all inducts (fault). when system starts. Need to automatically reset</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
<p><strong>Status Updates:</strong> Incomplete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="Beumer">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="Beumer">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items (3)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">BYPASS ATOC Auto induct reoccuring flase Jam</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
<span class="age-days">28 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Reassigned to Beumer</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Allocations are correct - wrong packages coming down</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
<span class="age-days">28 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S014024 CHUTE</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 will investigate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Auto induct - D back fireing packages that can go - also demissionier is off</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
<span class="age-days">28 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Auto induct - 7d</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 will investigate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="Beumer">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (12)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi-Auto Package marking X's</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Remark induct point X's on conveyance in permanent material (paint, ink, tape, etc.)</p>
|
||
<p><strong>Date Identified:</strong> 10/6/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - Beumer to start painting after sort tonight at VS-D
|
||
VS B C A complete... VS-d ECD 10/17 night
|
||
|
||
10/18 confirm if compete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">VS-D Auto-Induct Jams/Faults</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Training for ops on difference between jams/faults, ops seems to think all faults should clear themselves on auto-inducts, maybe something on minor piece</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - Bryan is working on similar issue at SAT9, Deepak from Amazon is helping, Jody will send people to investigate</p>
|
||
<p><strong>Image:</strong> fixed finger gaurds</p>
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Throughput Limit on SCADA</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-low">4 - Low</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Throughput Limit is being identified on SCADA and Grafana as an error code, despite not being in SFS. Determine root cause of Throughput Limits being triggered and assign them properly.</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 was used for testing is now disabled</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">SCADA Accurate Status Reads</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Beumer not sending full accurate lane status to AutStand for SCADA visualization. Beumer needs to send an updated Excel file for AutStand to update.</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/14/2025</p>
|
||
<p><strong>Status Updates:</strong> 10/14 - Autstand now has all of the program info from Beumer to connect statuses
|
||
10/17 resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Auto-Induct Restart</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> After an E-Stop and Restart, Auto-Induction didn't go through its auto clear cycle automatically, someone had to go to the local induction control station</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> 10/17 -- related to the global start? montor
|
||
confirmed that it works</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Operations requested the Problem Solve chutes from A and C to be disabled since not staffed</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> 10/17 -- Sherri asked Beumer (Bryan) to disable the 2 chutes from the sorter. Operations to advise when to re-enable</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">False Jam ( Rest every 6 mins)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S013018</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Reassigned to Beumer</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Air Knife over shooting takeaway conveyor</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Too many packages are falling in netting. Add add'l netting ? refocus air knife?</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-19</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/23 - Airknife out of alignment. Beumer adjusted but requested Silman to return to site to recalibrate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Inductions are going directly on bellowsco</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Experiencing too many items on bellow... causing sorter to stop</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Carrier disabled to shut down the sorter</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Sorter shutting down too often</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
<p><strong>Status Updates:</strong> 30% disable threshold... confirm reenable</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Estop not reporting on BGFusion/Scada</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Sorter stopped could not find root cause. Estop was triggered and not communicated</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-21</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Packages are being inducted on occupied trays</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Causing missorts and DBS/IBS/IOB faults that stop the sorter</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/23 - Beumer updated PLC to prevent issue but did nto work. Additional logs were addeed to trace root cause of issue (10/24 @730am)</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="Beumer">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (6)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Bypasses Not On Due to Auto-Induct Status</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Bypasses were turned off several times during testing</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> 10/14 - Bryan to update code tomorrow
|
||
10/15 - Bypasses had to be manually turned on when crossbelt stopped
|
||
10/16 - Fix applied, monitor</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Diverting onto Bellows from Bypass, adjust carrier aim</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Confirm divert points for auto and semi-auto inducts</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - Beumer is going to work on re-aiming some of these auto-inducts, retrain ops on induction angles</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Divert Points to Pallet Chutes</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Confirm divert points to pallet build chutes, light packages were landing in the wrong chutes or stuck in between</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - Check the chutes that have missorts and jams at the top
|
||
10/17 - chutes checked and made adjustments Monitor</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">IND2A-22 Carrier Induct Timing</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Check induct firing direction and timing at IND2A-22, a few packages were observed falling off the carriers being off to the edge</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 - beumer to monitor</p>
|
||
<p><strong>Image:</strong> IMG_4519.jpg</p>
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Induct 5B (Bypass induct C->) rejecting packages within MTBH</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> IND5B-5 (Induct platform VSB)</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - will verify Will check calibration, waiting on tool</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">auto inducts and inducts need to be restarted manually</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> auto inducts and inducts need to be restarted manually</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 The Induction Global Restart Correction completed . Since then we had a few instances when the safety doors were opened to test the new code. After closing the safety door the sorter started along with the inductions as expected.
|
||
; 11/09 - Issue Logged</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="Beumer">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (18)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">BYPASS ATOC Auto induct reoccuring flase Jam</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Reassigned to Beumer</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Allocations are correct - wrong packages coming down</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S014024 CHUTE</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 will investigate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Auto induct - D back fireing packages that can go - also demissionier is off</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Auto induct - 7d</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 will investigate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Packages are being directed to the wrong end of the chutes, AA had to take jiffy and scan to D2C</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Chute S014072</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 will investigate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">BUEMER scada - bypass is showing "die back" in yellow and futher up the belt is showing green. There is a disconnect. Packages arent able to move through in "die back" mode but the belt after is showing green, which looks to be good but isnt</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Bypass DA</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - will investigate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">false jam</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Lane S014024</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/19 - Reassigned to beumer, they control crossbelt chute jams</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">DBS sensors - heavier packages meeting weight requirement for main sorter triggering senors; causing sorter to shutdown</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Main Sorter</p>
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - need update for ops on how DBS works</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">jiffies getting caught in belows causing sorter to shutdown</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Cells on Main sorter</p>
|
||
<p><strong>Date Identified:</strong> 10/18/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Provide Bellow clearing procedures</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Document the process for clearing bellows for RME</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-17</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">At inducts evaluate why "conveyable" boxes are being rejected at induction</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Is aligner working as expected? Skewed boxes triggering as oversized</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-19</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Deep dive missorts (file shared)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
<p><strong>Status Updates:</strong> Incomplete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Aligner catch point on IND2C-s</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
<p><strong>Status Updates:</strong> Incomplete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Issue with needing to reset all inducts (fault). when system starts. Need to automatically reset</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-22</p>
|
||
|
||
<p><strong>Status Updates:</strong> Incomplete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Missorts</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> File with missorts shared.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-20</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/3 -- Missorts issue with chute trigger settings identified. All chutes evaluated and fixed on 10/30 will evaluate improvements with next Ops report</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Lane Not Available Metric too high</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
<p><strong>Status Updates:</strong> 11/3 - Working with Autstand conveyor ready flag as disabled ... will be addressed by full lane signal (fluidload only). Still need to do similar fix on bypass but need to evaluate when to trigger full lane (vs lane not available0</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Air knife is not firing properly leading to misfires</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Air knife is not firing properly leading to misfires</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-07</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Recalibrated but still having issues. Escalating to Beumer ; 11/07 - Camila to connect with Beumer on this issue and update</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">After a jam happens and it is reversed by the autoinduct. This requires human intervention to be reseted. The jam remains ready to be reset but doesnt provide any indication in SCADA so no one know it needs to be reset. Can we just autostart after a jam?</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> After a jam happens and it is reversed by the autoinduct. This requires human intervention to be reseted. The jam remains ready to be reset but doesnt provide any indication in SCADA so no one know it needs to be reset. Can we just autostart after a jam?</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-09</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/09 - Beumer is looking in to this. downtime is required to make changes for this.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Induct Jams</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Daily multiple jams on inducts / finger gaurds dislodged resulting in down time</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-11</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="Beumer/Datalogic">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">Beumer/Datalogic</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">3</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">1</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">1</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">1</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'Beumer/Datalogic')" data-status="all">All (3)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Beumer/Datalogic')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Beumer/Datalogic')" data-status="oldest_unaddressed">Oldest Unaddressed (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Beumer/Datalogic')" data-status="closed">Closed (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Beumer/Datalogic')" data-status="monitor">Monitor (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Beumer/Datalogic')" data-status="incomplete">Incomplete (1)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="Beumer/Datalogic">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Critical Priority (3 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">DHL packages are now in scope for processing. DHL labels need to be distributed to both Beumer and Amazon teams for proper handling. The plan is to have the Beumer team on-site to run test packages using one bottom scanner to validate the new barcode and label setup. If successful, the configuration will be deployed across all 36 Beumer scanners plus one DSC non-con unit. The team still needs to analyze 200 no-read and 200 multi-read images as part of the validation process.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> DHL packages are now in scope for processing. DHL labels need to be distributed to both Beumer and Amazon teams for proper handling. The plan is to have the Beumer team on-site to run test packages using one bottom scanner to validate the new barcode and label setup. If successful, the configuration will be deployed across all 36 Beumer scanners plus one DSC non-con unit. The team still needs to analyze 200 no-read and 200 multi-read images as part of the validation process.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-10</p>
|
||
<p><strong>Status Updates:</strong> 11/09 - Datalogic also updated the non-con scan tunnel for DHL labels.
|
||
11/07 - Action still in progress on the intralox sorter in terms of scanner calibration for DHL packages. The action is completed for the Xbelt. 11/6 COMPLETE - DHL labels are 100% fixed with zero scan tunnel errors for the last two days.
|
||
11/5 Update has been completed. Site to monitor PS to validate.
|
||
11/4 Two scan tunnels have been correct the remaining 7 will be completed by 11/5.
|
||
11/3 DHL label specification needs to be programmed in the scan tunnel logic.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The scan tunnels are experiencing elevated No-Reads and Multi-Reads issues. AE is now partnering with Datalogic and Beumer to identify root causes, with daily collaborative calls established. The VS-C Induct SCA001 has undergone calibration work including photo eye spacing measurements, AV7000 scan distance adjustment to 125mm, and camera calibration, with ongoing monitoring of read rates. Datalogic is continuing to focus on SCA001, working on timing/tracking adjustments and conducting image analysis of 200 no-read and 200 multi-read samples to identify patterns.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The scan tunnels are experiencing elevated No-Reads and Multi-Reads issues. AE is now partnering with Datalogic and Beumer to identify root causes, with daily collaborative calls established. The VS-C Induct SCA001 has undergone calibration work including photo eye spacing measurements, AV7000 scan distance adjustment to 125mm, and camera calibration, with ongoing monitoring of read rates. Datalogic is continuing to focus on SCA001, working on timing/tracking adjustments and conducting image analysis of 200 no-read and 200 multi-read samples to identify patterns.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-16</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Site is still experiencing high No Reads. Data from 11/9 (4am to 4am) shows 7.0% No Reads (48,032) and 5.1% Multi-Reads (34,804). (Grifana)
|
||
11/09 - All updates are complete. Amazon team is monitoring performance. Will close out after a week of consistent results. 96% good read rate from 11/08 data.
|
||
11/07 - The VS-C induct has been calibrated and is now working. Tech needs to check if a no-read is a true no-read or a damaged/misaligned label. We will continue monitoring.
|
||
11/6 - No Update
|
||
11/5 - Per FE Controls and Beumer deep dive: Grafana receives S01 messages as items go through each scan tunnel and adds them together, creating an "inflated" scan defect number. Beumer only sends the code on a true scan, then the code moves through the sorter attached to the carrier, showing the true defect count that is not inflated. Deep dives are still happening. Should have analysis from Datalogic by 11/6 for review by FE Controls to ensure the Beumer defect count is correct. If correct, site will only be able to see true defects on BG Fusion and will not be able to rely on Grafana data to make operational decisions, deep dive, or troubleshoot issues. @hakerp will look into a defect dashboard as an alternative.
|
||
11/4 - Grafana and BG Fusion do not match in scan tunnel defects (variance of 20%+). @davoste is deep diving the issue and will have a recap for the 11/5 daily call. All scan tunnels will have the logic update completed by 11/5.
|
||
11/3 - Four scan tunnels will be completed with logic change on 11/3; remaining 5 to be completed 11/5.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The program required for accessing package images for detailed troubleshooting is currently inaccessible to remote teams. The VLAN was not converted to off-corp as planned and remains on-corp, which is an IT issue requiring deep investigation. Beumer/Datalogic needs to provide Amazon with a detailed network architecture drawing to understand how everything is connected and supposed to work. This is blocking remote troubleshooting capabilities with ownership under IT/Datalogic.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The program required for accessing package images for detailed troubleshooting is currently inaccessible to remote teams. The VLAN was not converted to off-corp as planned and remains on-corp, which is an IT issue requiring deep investigation. Beumer/Datalogic needs to provide Amazon with a detailed network architecture drawing to understand how everything is connected and supposed to work. This is blocking remote troubleshooting capabilities with ownership under IT/Datalogic.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Vlan deployed on 11/7. IP's shared with DL to remap the connections. Testing.
|
||
11/07 - Local IT has a MCM to update VLANs for remote access to work. Waiting on update from IT.
|
||
11/6 No update
|
||
11/5 Update from local IT for VLAN deployment - working on getting MCMs written and are trying to push them through for Friday Morning.
|
||
(Seems like there needs to be 7 total MCMs).
|
||
11/4 @deesant is working to bring online before Peak. If unable to rectify, onsite (vendor/OE) support schedule will be used to ensure site is able to troubleshoot and resolve issue without remote access.
|
||
11/3 Current timeline is the access will not be able to be granted until Q1 2026</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="Beumer/Datalogic">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="Beumer/Datalogic">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The program required for accessing package images for detailed troubleshooting is currently inaccessible to remote teams. The VLAN was not converted to off-corp as planned and remains on-corp, which is an IT issue requiring deep investigation. Beumer/Datalogic needs to provide Amazon with a detailed network architecture drawing to understand how everything is connected and supposed to work. This is blocking remote troubleshooting capabilities with ownership under IT/Datalogic.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
<span class="age-days">29 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The program required for accessing package images for detailed troubleshooting is currently inaccessible to remote teams. The VLAN was not converted to off-corp as planned and remains on-corp, which is an IT issue requiring deep investigation. Beumer/Datalogic needs to provide Amazon with a detailed network architecture drawing to understand how everything is connected and supposed to work. This is blocking remote troubleshooting capabilities with ownership under IT/Datalogic.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Vlan deployed on 11/7. IP's shared with DL to remap the connections. Testing.
|
||
11/07 - Local IT has a MCM to update VLANs for remote access to work. Waiting on update from IT.
|
||
11/6 No update
|
||
11/5 Update from local IT for VLAN deployment - working on getting MCMs written and are trying to push them through for Friday Morning.
|
||
(Seems like there needs to be 7 total MCMs).
|
||
11/4 @deesant is working to bring online before Peak. If unable to rectify, onsite (vendor/OE) support schedule will be used to ensure site is able to troubleshoot and resolve issue without remote access.
|
||
11/3 Current timeline is the access will not be able to be granted until Q1 2026</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="Beumer/Datalogic">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">DHL packages are now in scope for processing. DHL labels need to be distributed to both Beumer and Amazon teams for proper handling. The plan is to have the Beumer team on-site to run test packages using one bottom scanner to validate the new barcode and label setup. If successful, the configuration will be deployed across all 36 Beumer scanners plus one DSC non-con unit. The team still needs to analyze 200 no-read and 200 multi-read images as part of the validation process.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> DHL packages are now in scope for processing. DHL labels need to be distributed to both Beumer and Amazon teams for proper handling. The plan is to have the Beumer team on-site to run test packages using one bottom scanner to validate the new barcode and label setup. If successful, the configuration will be deployed across all 36 Beumer scanners plus one DSC non-con unit. The team still needs to analyze 200 no-read and 200 multi-read images as part of the validation process.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-10</p>
|
||
<p><strong>Status Updates:</strong> 11/09 - Datalogic also updated the non-con scan tunnel for DHL labels.
|
||
11/07 - Action still in progress on the intralox sorter in terms of scanner calibration for DHL packages. The action is completed for the Xbelt. 11/6 COMPLETE - DHL labels are 100% fixed with zero scan tunnel errors for the last two days.
|
||
11/5 Update has been completed. Site to monitor PS to validate.
|
||
11/4 Two scan tunnels have been correct the remaining 7 will be completed by 11/5.
|
||
11/3 DHL label specification needs to be programmed in the scan tunnel logic.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="Beumer/Datalogic">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The scan tunnels are experiencing elevated No-Reads and Multi-Reads issues. AE is now partnering with Datalogic and Beumer to identify root causes, with daily collaborative calls established. The VS-C Induct SCA001 has undergone calibration work including photo eye spacing measurements, AV7000 scan distance adjustment to 125mm, and camera calibration, with ongoing monitoring of read rates. Datalogic is continuing to focus on SCA001, working on timing/tracking adjustments and conducting image analysis of 200 no-read and 200 multi-read samples to identify patterns.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The scan tunnels are experiencing elevated No-Reads and Multi-Reads issues. AE is now partnering with Datalogic and Beumer to identify root causes, with daily collaborative calls established. The VS-C Induct SCA001 has undergone calibration work including photo eye spacing measurements, AV7000 scan distance adjustment to 125mm, and camera calibration, with ongoing monitoring of read rates. Datalogic is continuing to focus on SCA001, working on timing/tracking adjustments and conducting image analysis of 200 no-read and 200 multi-read samples to identify patterns.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-16</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Site is still experiencing high No Reads. Data from 11/9 (4am to 4am) shows 7.0% No Reads (48,032) and 5.1% Multi-Reads (34,804). (Grifana)
|
||
11/09 - All updates are complete. Amazon team is monitoring performance. Will close out after a week of consistent results. 96% good read rate from 11/08 data.
|
||
11/07 - The VS-C induct has been calibrated and is now working. Tech needs to check if a no-read is a true no-read or a damaged/misaligned label. We will continue monitoring.
|
||
11/6 - No Update
|
||
11/5 - Per FE Controls and Beumer deep dive: Grafana receives S01 messages as items go through each scan tunnel and adds them together, creating an "inflated" scan defect number. Beumer only sends the code on a true scan, then the code moves through the sorter attached to the carrier, showing the true defect count that is not inflated. Deep dives are still happening. Should have analysis from Datalogic by 11/6 for review by FE Controls to ensure the Beumer defect count is correct. If correct, site will only be able to see true defects on BG Fusion and will not be able to rely on Grafana data to make operational decisions, deep dive, or troubleshoot issues. @hakerp will look into a defect dashboard as an alternative.
|
||
11/4 - Grafana and BG Fusion do not match in scan tunnel defects (variance of 20%+). @davoste is deep diving the issue and will have a recap for the 11/5 daily call. All scan tunnels will have the logic update completed by 11/5.
|
||
11/3 - Four scan tunnels will be completed with logic change on 11/3; remaining 5 to be completed 11/5.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="Beumer/Datalogic">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">The program required for accessing package images for detailed troubleshooting is currently inaccessible to remote teams. The VLAN was not converted to off-corp as planned and remains on-corp, which is an IT issue requiring deep investigation. Beumer/Datalogic needs to provide Amazon with a detailed network architecture drawing to understand how everything is connected and supposed to work. This is blocking remote troubleshooting capabilities with ownership under IT/Datalogic.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> The program required for accessing package images for detailed troubleshooting is currently inaccessible to remote teams. The VLAN was not converted to off-corp as planned and remains on-corp, which is an IT issue requiring deep investigation. Beumer/Datalogic needs to provide Amazon with a detailed network architecture drawing to understand how everything is connected and supposed to work. This is blocking remote troubleshooting capabilities with ownership under IT/Datalogic.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-15</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/10 - Vlan deployed on 11/7. IP's shared with DL to remap the connections. Testing.
|
||
11/07 - Local IT has a MCM to update VLANs for remote access to work. Waiting on update from IT.
|
||
11/6 No update
|
||
11/5 Update from local IT for VLAN deployment - working on getting MCMs written and are trying to push them through for Friday Morning.
|
||
(Seems like there needs to be 7 total MCMs).
|
||
11/4 @deesant is working to bring online before Peak. If unable to rectify, onsite (vendor/OE) support schedule will be used to ensure site is able to troubleshoot and resolve issue without remote access.
|
||
11/3 Current timeline is the access will not be able to be granted until Q1 2026</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="Caljan">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">Caljan</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">4</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">0</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">4</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'Caljan')" data-status="all">All (4)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Caljan')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Caljan')" data-status="oldest_unaddressed">Oldest Unaddressed (3)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Caljan')" data-status="closed">Closed (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Caljan')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Caljan')" data-status="incomplete">Incomplete (4)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="Caljan">
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (3 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Photoeyes at Caljan not wired properly</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Photoeyes stop the line vs feeding when blocked</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> Autstand jumped out the photoeyes to get them operational
|
||
10/17 SS contacted Caljan... waiting on date for tech</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Maxx Reach at DD 332 not working
|
||
https://t.corp.amazon.com/V1969041198</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> OB Fluid</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 Sherri contacted Caljan and arranged for RME to have remote tech support</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Max reach 119 PE at top of max reach needs to be adjusted , also having to reset line at times for it to move</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Reassigned to Caljan</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">No Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Max Reach 100% PE logic is backwards All 300 and 100 DD</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Outbound</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Reassigned to Caljan</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="Caljan">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="Caljan">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items (3)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Photoeyes at Caljan not wired properly</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
<span class="age-days">29 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Photoeyes stop the line vs feeding when blocked</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> Autstand jumped out the photoeyes to get them operational
|
||
10/17 SS contacted Caljan... waiting on date for tech</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Maxx Reach at DD 332 not working
|
||
https://t.corp.amazon.com/V1969041198</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
<span class="age-days">29 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> OB Fluid</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 Sherri contacted Caljan and arranged for RME to have remote tech support</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Max Reach 100% PE logic is backwards All 300 and 100 DD</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
<span class="age-days">28 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Outbound</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Reassigned to Caljan</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="Caljan">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No closed items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="Caljan">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="Caljan">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (4)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Photoeyes at Caljan not wired properly</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Photoeyes stop the line vs feeding when blocked</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> Autstand jumped out the photoeyes to get them operational
|
||
10/17 SS contacted Caljan... waiting on date for tech</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Maxx Reach at DD 332 not working
|
||
https://t.corp.amazon.com/V1969041198</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> OB Fluid</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 Sherri contacted Caljan and arranged for RME to have remote tech support</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Max Reach 100% PE logic is backwards All 300 and 100 DD</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Outbound</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Reassigned to Caljan</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Max reach 119 PE at top of max reach needs to be adjusted , also having to reset line at times for it to move</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> KK 10/18 - Reassigned to Caljan</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="DCS">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">DCS</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">25</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">21</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">1</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">3</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'DCS')" data-status="all">All (25)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS')" data-status="oldest_unaddressed">Oldest Unaddressed (3)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS')" data-status="closed">Closed (21)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS')" data-status="monitor">Monitor (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS')" data-status="incomplete">Incomplete (3)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="DCS">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Critical Priority (4 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Flow turn Belt Replacement</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Flow turn belts incorrectly manufactured and need to be replaced</p>
|
||
<p><strong>Date Identified:</strong> 10/10/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/29 final belt replacement scheduled for midnite tonight 11/3 - all belts have been replaced</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL7-17 Belt needs to be replaced (again) RME installation (ripped edges, lacing)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-18</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL21-24 Failed (belts and shaft)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-20</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/21/25 - repair completed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NCS1-1 aligner belt failed</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Belt failed prior to flow splitter. Replaced with belt from noncon 2 (using only non con 1) until belt is delivered.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-01</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/3 - still waiting on belt to be delivered</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (17 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi-Auto Phantom Jams</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Dust accumulation on the reflectors incorrectly creating jam states on the funnels leading to semi-auto inducts</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 - DCS surveyed... on going.
|
||
10/18 Belts being cauterized to eliminate the flaying . Will update with estimated completion date 10/19 -- in process
|
||
10/22: Inbound Completed; Working on Bypass and PS conveyance</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NC End of Sorter Chute</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Packages getting stuck in chute at dead plate and rollers. Need to look at a mechanical fix to eliminate issue, possibly extend the dead plate.</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 --- Changed the PE location.. to trigger the MDR. monitor may need to add UHMW</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Catch point at DD118 fluid load</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> 10/17 -Weld failed. DCS bolted sidepan. Check other pans</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NC flow splitter has worn rollers</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> pop up rollers on flow splitter are worn. replace wheels, assure that installation is adjusted/fine-tuned</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - still pending
|
||
10/22: awaiting Down time window will take several down times to complete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">oil leak in NON CON near chute S02-202CH</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S02-202CH</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> No Oil Present at Chute (Fire Suppression Pipe is Leaking)</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">oil leak in NON CON near chute QAA-3CH</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> QAA-3CH</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> No Oil Present at Chute</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">packages being re inducted into ps bottom belt - hits the belt - needs to be raised</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> PS collector re induct chutes</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> Cannot raise belt</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Divert arms are to high and are causing jiffys to get stuck under the arm when diverting</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Semi induct A</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - pending</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS chute lip is catching ps boxes</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> QAB-2CH</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> Pending</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Maint jack for tippers</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 - Confirmed that jack was not received/onsite here or MTN2. Asked DCS to confirm if ordered with the tippers.
|
||
10/22: PO Pending for 1 Jack
|
||
10/23: ETA Shipping Date of Tipper Jack is 10/31/2025</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non Con Chute/Maint access. Need Latch upgrade</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-10</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10.29 SSI will be on site to evaluate /repair 10/30. 11/3 - SSI completed their evaluation, need to replace/rebuild over 40 latches</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Motor falling on HSQ gappers.. 2x (3:1 merge)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> upgrade the bolts</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PRS4-2 Motor Replacement</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Motor Oreded will update when I have an ETA ( Tryignto get this overnight)</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-26</p>
|
||
|
||
<p><strong>Status Updates:</strong> Pending Ship Date</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">) There is a catchpoint of bent metal that is sticking out from the tail assembly on PS10-1 where it transitions to PS11-1. This is catching polys during operation. Jesse is going to look into making proper modifications to eliminate this.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Catached Point in two area's Both have been completed</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-04</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-05</p>
|
||
<p><strong>Status Updates:</strong> 11/4 - Wes Matthews reviewed with Jesse</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">2) When product from PS10-1 is flowing towards PS11-1, there is no snowplow and instead the slide just dead ends with a corner of sidepan. I’ve asked Jesse to look into fabricating a UHMW piece that could bridge this corner to push products down onto the belt.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Completed</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-04</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-05</p>
|
||
<p><strong>Status Updates:</strong> 11/4 Wes Matthews reviewed with Jesse</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi-Auto Chute Sidepan Reinforcement</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Sidepans are flimsy and need to be reinforced; when a heavy box hits the side, the guarding moves, mistakenly blocking the jam photoeye</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 -- investigated... no issues identified monitor
|
||
11/3: Nothing Mechanical we can do to frim up the side guard it is stanless steel</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">3) The black UHMW strip under the belt which transitions the belt from slider bed to tail roller is too sharp and is shaving the bottom side of the belt. Jesse and his team are going to look into pulling this uhmw strip out, properly chamfering it and then re-installing.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-11-04</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/4 Wes Matthews reviewed with Jesse</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">Other Priority (2 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NC Sorter Aligner</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> NC Sorter Aligner has a catch point at the exit, uhmw transfer plates on vertical belt and conveyor tplate</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> 10/17 - fixed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Add air pressure valves (autstand request to DCS)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - no update
|
||
10/22: A waiting CR</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">No Priority (2 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL4-15 damaged belt</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS6-3</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Noisy when running, side pan is very warm to the touch</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-18</p>
|
||
|
||
<p><strong>Status Updates:</strong> F14041</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="DCS">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="DCS">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items (3)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NCS1-1 aligner belt failed</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
<span class="age-days">12 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Belt failed prior to flow splitter. Replaced with belt from noncon 2 (using only non con 1) until belt is delivered.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-01</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/3 - still waiting on belt to be delivered</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">3) The black UHMW strip under the belt which transitions the belt from slider bed to tail roller is too sharp and is shaving the bottom side of the belt. Jesse and his team are going to look into pulling this uhmw strip out, properly chamfering it and then re-installing.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
<span class="age-days">9 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-11-04</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/4 Wes Matthews reviewed with Jesse</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Add air pressure valves (autstand request to DCS)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - no update
|
||
10/22: A waiting CR</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="DCS">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (21)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Flow turn Belt Replacement</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Flow turn belts incorrectly manufactured and need to be replaced</p>
|
||
<p><strong>Date Identified:</strong> 10/10/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/29 final belt replacement scheduled for midnite tonight 11/3 - all belts have been replaced</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi-Auto Phantom Jams</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Dust accumulation on the reflectors incorrectly creating jam states on the funnels leading to semi-auto inducts</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 - DCS surveyed... on going.
|
||
10/18 Belts being cauterized to eliminate the flaying . Will update with estimated completion date 10/19 -- in process
|
||
10/22: Inbound Completed; Working on Bypass and PS conveyance</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NC End of Sorter Chute</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Packages getting stuck in chute at dead plate and rollers. Need to look at a mechanical fix to eliminate issue, possibly extend the dead plate.</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 --- Changed the PE location.. to trigger the MDR. monitor may need to add UHMW</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NC Sorter Aligner</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> NC Sorter Aligner has a catch point at the exit, uhmw transfer plates on vertical belt and conveyor tplate</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/17</p>
|
||
<p><strong>Status Updates:</strong> 10/17 - fixed.</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Catch point at DD118 fluid load</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> 10/17 -Weld failed. DCS bolted sidepan. Check other pans</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NC flow splitter has worn rollers</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> pop up rollers on flow splitter are worn. replace wheels, assure that installation is adjusted/fine-tuned</p>
|
||
<p><strong>Date Identified:</strong> 10/17</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - still pending
|
||
10/22: awaiting Down time window will take several down times to complete</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">oil leak in NON CON near chute S02-202CH</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> S02-202CH</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> No Oil Present at Chute (Fire Suppression Pipe is Leaking)</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">oil leak in NON CON near chute QAA-3CH</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> QAA-3CH</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> No Oil Present at Chute</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">packages being re inducted into ps bottom belt - hits the belt - needs to be raised</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> PS collector re induct chutes</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> Cannot raise belt</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Divert arms are to high and are causing jiffys to get stuck under the arm when diverting</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Semi induct A</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - pending</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS chute lip is catching ps boxes</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> QAB-2CH</p>
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> Pending</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Maint jack for tippers</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/17/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 - Confirmed that jack was not received/onsite here or MTN2. Asked DCS to confirm if ordered with the tippers.
|
||
10/22: PO Pending for 1 Jack
|
||
10/23: ETA Shipping Date of Tipper Jack is 10/31/2025</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL4-15 damaged belt</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS6-3</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Noisy when running, side pan is very warm to the touch</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-18</p>
|
||
|
||
<p><strong>Status Updates:</strong> F14041</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL7-17 Belt needs to be replaced (again) RME installation (ripped edges, lacing)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-18</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non Con Chute/Maint access. Need Latch upgrade</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-10</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10.29 SSI will be on site to evaluate /repair 10/30. 11/3 - SSI completed their evaluation, need to replace/rebuild over 40 latches</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL21-24 Failed (belts and shaft)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-10-20</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/21/25 - repair completed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Motor falling on HSQ gappers.. 2x (3:1 merge)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> upgrade the bolts</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PRS4-2 Motor Replacement</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Motor Oreded will update when I have an ETA ( Tryignto get this overnight)</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-26</p>
|
||
|
||
<p><strong>Status Updates:</strong> Pending Ship Date</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">) There is a catchpoint of bent metal that is sticking out from the tail assembly on PS10-1 where it transitions to PS11-1. This is catching polys during operation. Jesse is going to look into making proper modifications to eliminate this.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Catached Point in two area's Both have been completed</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-04</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-05</p>
|
||
<p><strong>Status Updates:</strong> 11/4 - Wes Matthews reviewed with Jesse</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">2) When product from PS10-1 is flowing towards PS11-1, there is no snowplow and instead the slide just dead ends with a corner of sidepan. I’ve asked Jesse to look into fabricating a UHMW piece that could bridge this corner to push products down onto the belt.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Completed</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-04</p>
|
||
<p><strong>Date Completed:</strong> 2025-11-05</p>
|
||
<p><strong>Status Updates:</strong> 11/4 Wes Matthews reviewed with Jesse</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="DCS">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Semi-Auto Chute Sidepan Reinforcement</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Sidepans are flimsy and need to be reinforced; when a heavy box hits the side, the guarding moves, mistakenly blocking the jam photoeye</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 -- investigated... no issues identified monitor
|
||
11/3: Nothing Mechanical we can do to frim up the side guard it is stanless steel</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="DCS">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (3)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Add air pressure valves (autstand request to DCS)</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
<p><strong>Status Updates:</strong> 10/18 - no update
|
||
10/22: A waiting CR</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">NCS1-1 aligner belt failed</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Belt failed prior to flow splitter. Replaced with belt from noncon 2 (using only non con 1) until belt is delivered.</p>
|
||
<p><strong>Date Identified:</strong> 2025-11-01</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/3 - still waiting on belt to be delivered</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">3) The black UHMW strip under the belt which transitions the belt from slider bed to tail roller is too sharp and is shaving the bottom side of the belt. Jesse and his team are going to look into pulling this uhmw strip out, properly chamfering it and then re-installing.</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 2025-11-04</p>
|
||
|
||
<p><strong>Status Updates:</strong> 11/4 Wes Matthews reviewed with Jesse</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="DCS/Autstand">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">DCS/Autstand</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">1</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">1</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'DCS/Autstand')" data-status="all">All (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/Autstand')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/Autstand')" data-status="oldest_unaddressed">Oldest Unaddressed (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/Autstand')" data-status="closed">Closed (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/Autstand')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/Autstand')" data-status="incomplete">Incomplete (0)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="DCS/Autstand">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">No Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">caljan at comm cable was ripped out</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> dock door 223</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-21</p>
|
||
<p><strong>Status Updates:</strong> KK 10/21 - Investigated the unit, did not see anything unusual. Unit is working fine</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="DCS/Autstand">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="DCS/Autstand">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No unaddressed items</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="DCS/Autstand">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">caljan at comm cable was ripped out</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> dock door 223</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-21</p>
|
||
<p><strong>Status Updates:</strong> KK 10/21 - Investigated the unit, did not see anything unusual. Unit is working fine</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="DCS/Autstand">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="DCS/Autstand">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No incomplete items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="DCS/Flow-Turn">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">DCS/Flow-Turn</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">1</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">1</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'DCS/Flow-Turn')" data-status="all">All (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/Flow-Turn')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/Flow-Turn')" data-status="oldest_unaddressed">Oldest Unaddressed (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/Flow-Turn')" data-status="closed">Closed (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/Flow-Turn')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/Flow-Turn')" data-status="incomplete">Incomplete (0)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="DCS/Flow-Turn">
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS3-1 merge</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Shaft walked causing the belts to come off track and destroy 2 belts</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-18</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> AM 10/19 - DCS repaired this merge and replaced the 2 belts. This needs to be monitored</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="DCS/Flow-Turn">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="DCS/Flow-Turn">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No unaddressed items</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="DCS/Flow-Turn">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">PS3-1 merge</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Shaft walked causing the belts to come off track and destroy 2 belts</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-18</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-19</p>
|
||
<p><strong>Status Updates:</strong> AM 10/19 - DCS repaired this merge and replaced the 2 belts. This needs to be monitored</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="DCS/Flow-Turn">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="DCS/Flow-Turn">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No incomplete items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="DCS/RME">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">DCS/RME</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">1</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">1</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'DCS/RME')" data-status="all">All (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/RME')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/RME')" data-status="oldest_unaddressed">Oldest Unaddressed (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/RME')" data-status="closed">Closed (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/RME')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'DCS/RME')" data-status="incomplete">Incomplete (0)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="DCS/RME">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">No Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL7-17 Belt has a rip</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Rip in belt the size of a dollar bill</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-18</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> AM 10/19 - RME replaced this belt</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="DCS/RME">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="DCS/RME">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No unaddressed items</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="DCS/RME">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL7-17 Belt has a rip</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Rip in belt the size of a dollar bill</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-18</p>
|
||
<p><strong>Date Completed:</strong> 2025-10-18</p>
|
||
<p><strong>Status Updates:</strong> AM 10/19 - RME replaced this belt</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="DCS/RME">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="DCS/RME">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No incomplete items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="Datalogic">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">Datalogic</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">5</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">0</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">1</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">4</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'Datalogic')" data-status="all">All (5)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Datalogic')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Datalogic')" data-status="oldest_unaddressed">Oldest Unaddressed (3)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Datalogic')" data-status="closed">Closed (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Datalogic')" data-status="monitor">Monitor (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Datalogic')" data-status="incomplete">Incomplete (4)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="Datalogic">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Critical Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Add DHL label to Scan tunnel valid message</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> DHL label was not in orignal spec. Need to be able to identify that label and filter out other barcodes.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-27</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (2 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">No Read Rates - Trigger Timing Concerns</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Confirm that the trigger timing from yesterday is fully resolved</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 - S01 ad. trigger was moved. appears to be resolved. monitoring</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">High Multi-Label Read Rate</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Unexpectedly high multi-read rate from scanners during LOT</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - Datalogic prioritzing deep dive on these issues to identify root cause
|
||
10/17 - in process sa01 ab still has issue. investigating 10/19= Modification today, monitor 11/3 - DAta logic is reconfiguring all scan tunnels. SCA01, SCA02 complete. SCA03 and SCA04 to be completed over night 11/3</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">Other Priority (2 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Long-Term Error Tracking Solution</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Currently, manual pull of all images from Datalogic programs is required to ID issues</p>
|
||
<p><strong>Date Identified:</strong> 10/8/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17- DL is proposes to get 2D images. Jody to follow up</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Pull stats for error codes from Datalogic</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Need ability to pull error code stats from Datalogic</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 -- Jody to follow up with DL</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="Datalogic">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="Datalogic">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items (3)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Long-Term Error Tracking Solution</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
<span class="age-days">36 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Currently, manual pull of all images from Datalogic programs is required to ID issues</p>
|
||
<p><strong>Date Identified:</strong> 10/8/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17- DL is proposes to get 2D images. Jody to follow up</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">High Multi-Label Read Rate</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
<span class="age-days">30 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Unexpectedly high multi-read rate from scanners during LOT</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - Datalogic prioritzing deep dive on these issues to identify root cause
|
||
10/17 - in process sa01 ab still has issue. investigating 10/19= Modification today, monitor 11/3 - DAta logic is reconfiguring all scan tunnels. SCA01, SCA02 complete. SCA03 and SCA04 to be completed over night 11/3</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Pull stats for error codes from Datalogic</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
<span class="age-days">30 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Need ability to pull error code stats from Datalogic</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 -- Jody to follow up with DL</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="Datalogic">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No closed items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="Datalogic">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">No Read Rates - Trigger Timing Concerns</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Monitor</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Confirm that the trigger timing from yesterday is fully resolved</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 - S01 ad. trigger was moved. appears to be resolved. monitoring</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="Datalogic">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (4)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">High Multi-Label Read Rate</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Unexpectedly high multi-read rate from scanners during LOT</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/14 - Datalogic prioritzing deep dive on these issues to identify root cause
|
||
10/17 - in process sa01 ab still has issue. investigating 10/19= Modification today, monitor 11/3 - DAta logic is reconfiguring all scan tunnels. SCA01, SCA02 complete. SCA03 and SCA04 to be completed over night 11/3</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Long-Term Error Tracking Solution</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Currently, manual pull of all images from Datalogic programs is required to ID issues</p>
|
||
<p><strong>Date Identified:</strong> 10/8/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17- DL is proposes to get 2D images. Jody to follow up</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Pull stats for error codes from Datalogic</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">3 - Med</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Need ability to pull error code stats from Datalogic</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> 10/17 -- Jody to follow up with DL</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Add DHL label to Scan tunnel valid message</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> DHL label was not in orignal spec. Need to be able to identify that label and filter out other barcodes.</p>
|
||
<p><strong>Date Identified:</strong> 2025-10-27</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="FMH/Gorbel">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">FMH/Gorbel</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">1</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">1</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'FMH/Gorbel')" data-status="all">All (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'FMH/Gorbel')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'FMH/Gorbel')" data-status="oldest_unaddressed">Oldest Unaddressed (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'FMH/Gorbel')" data-status="closed">Closed (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'FMH/Gorbel')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'FMH/Gorbel')" data-status="incomplete">Incomplete (0)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="FMH/Gorbel">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">No Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Maxx reach controls do not function as prescribed</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> All OB fluid maxxx reaches</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> Gorbel and FMH on site for training/ support</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="FMH/Gorbel">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="FMH/Gorbel">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No unaddressed items</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="FMH/Gorbel">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Maxx reach controls do not function as prescribed</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> All OB fluid maxxx reaches</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> Gorbel and FMH on site for training/ support</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="FMH/Gorbel">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="FMH/Gorbel">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No incomplete items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="Gorbel">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">Gorbel</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">2</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">2</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'Gorbel')" data-status="all">All (2)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Gorbel')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Gorbel')" data-status="oldest_unaddressed">Oldest Unaddressed (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Gorbel')" data-status="closed">Closed (2)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Gorbel')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Gorbel')" data-status="incomplete">Incomplete (0)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="Gorbel">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Critical Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Destuffit fault at DD225</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Contact failed and estop jumped out ... could not retract/extend unit</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">DD218-DESTUFF-IT not properly working packing not able to climb up</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> DD218 Destuff-it</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="Gorbel">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="Gorbel">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No unaddressed items</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="Gorbel">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (2)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Destuffit fault at DD225</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-critical">1 - Critical</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Contact failed and estop jumped out ... could not retract/extend unit</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">DD218-DESTUFF-IT not properly working packing not able to climb up</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> DD218 Destuff-it</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="Gorbel">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="Gorbel">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No incomplete items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="MFO (Amazon)">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">MFO (Amazon)</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">1</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">1</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'MFO (Amazon)')" data-status="all">All (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'MFO (Amazon)')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'MFO (Amazon)')" data-status="oldest_unaddressed">Oldest Unaddressed (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'MFO (Amazon)')" data-status="closed">Closed (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'MFO (Amazon)')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'MFO (Amazon)')" data-status="incomplete">Incomplete (0)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="MFO (Amazon)">
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Confirm D2C is Working</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Verify all D2C lanes are mapped properly</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/14/2025</p>
|
||
<p><strong>Status Updates:</strong> 10/18 -- complete confirmed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="MFO (Amazon)">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="MFO (Amazon)">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No unaddressed items</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="MFO (Amazon)">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Confirm D2C is Working</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Verify all D2C lanes are mapped properly</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
<p><strong>Date Completed:</strong> 10/14/2025</p>
|
||
<p><strong>Status Updates:</strong> 10/18 -- complete confirmed</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="MFO (Amazon)">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="MFO (Amazon)">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No incomplete items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="MISC">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">MISC</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">35</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">2</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">33</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'MISC')" data-status="all">All (35)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'MISC')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'MISC')" data-status="oldest_unaddressed">Oldest Unaddressed (3)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'MISC')" data-status="closed">Closed (2)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'MISC')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'MISC')" data-status="incomplete">Incomplete (33)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="MISC">
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (2 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non - Con Jam rest button -</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> NCPRS2-1CH</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> duplicate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Auto inducts / By passes do not start up with scata -</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">Other Priority (28 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL21</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -Created a JAM on UL21-3, unable to restart line by pushing start button or system start/reset button on control panel
|
||
-CP Stacklight AMBER beacon does not turn on in Fault/Jam Condition</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL20</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -CP</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL19</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL18</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL17</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL16</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL15</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL14</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL13</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL12</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL11</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL10</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL9</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -UL9-5</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL8</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -UL8-4</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL7</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -UL7-3</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL6</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL5</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL4</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL3</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -PE</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL2</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -UL2-3</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL1</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -Caused Jam Condition on UL1-3, Cannot restart system from CP reset/start button, or local start buttons in that section. Have to walk downstream to reset.
|
||
-UL1-3 PE jam timers need to be lower, timer too long to detect Jams
|
||
-Jam Beacon not turning on
|
||
-CP AMBER stack light not turning on during fault/jam condition
|
||
-UL1-10B PE stops conveyor in front of it (UL1-11) and jam on SCADA shows as UL1-11</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">MCM05 Chutes</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Beumer</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> -Chute</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-12 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UI027 / BYAB-15</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Austand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> -Jam</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-12 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UI028 / BYCB</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Austand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> -Jam</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-12 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UI024 / UI025</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Austand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> -Jam</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-12 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">2 - High</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">In Progress</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">3 - Med</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Monitoring</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">4 - Low</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Complete</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">No Priority (5 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">supply cabinet in NON Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> NON Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">drop zone banner in Non Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> drop zone banner in Non Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">printer station at both ends in Non Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">5s area for emtpy carts in Non Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Fans in Non Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="MISC">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="MISC">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items (3)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">supply cabinet in NON Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
<span class="age-days">28 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> NON Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">drop zone banner in Non Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
<span class="age-days">28 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> drop zone banner in Non Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">printer station at both ends in Non Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
<span class="age-days">28 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="MISC">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (2)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Non - Con Jam rest button -</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> NCPRS2-1CH</p>
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> duplicate</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Auto inducts / By passes do not start up with scata -</div>
|
||
<div class="badges">
|
||
<span class="badge badge-success">Complete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> 10/15/2025</p>
|
||
|
||
<p><strong>Status Updates:</strong> resolved</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="MISC">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="MISC">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (33)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">supply cabinet in NON Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> NON Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">drop zone banner in Non Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> drop zone banner in Non Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">printer station at both ends in Non Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">5s area for emtpy carts in Non Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Fans in Non Con</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Non Con</p>
|
||
<p><strong>Date Identified:</strong> 10/16/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL21</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -Created a JAM on UL21-3, unable to restart line by pushing start button or system start/reset button on control panel
|
||
-CP Stacklight AMBER beacon does not turn on in Fault/Jam Condition</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL20</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -CP</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL19</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL18</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL17</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL16</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL15</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL14</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL13</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL12</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL11</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL10</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL9</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -UL9-5</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL8</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -UL8-4</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL7</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -UL7-3</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL6</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL5</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL4</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL3</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -PE</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL2</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -UL2-3</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UL1</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Autstand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> (2) High</p>
|
||
<p><strong>Date Identified:</strong> -Caused Jam Condition on UL1-3, Cannot restart system from CP reset/start button, or local start buttons in that section. Have to walk downstream to reset.
|
||
-UL1-3 PE jam timers need to be lower, timer too long to detect Jams
|
||
-Jam Beacon not turning on
|
||
-CP AMBER stack light not turning on during fault/jam condition
|
||
-UL1-10B PE stops conveyor in front of it (UL1-11) and jam on SCADA shows as UL1-11</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-11 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">MCM05 Chutes</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Beumer</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> -Chute</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-12 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UI027 / BYAB-15</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Austand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> -Jam</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-12 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UI028 / BYCB</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Austand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> -Jam</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-12 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">UI024 / UI025</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Austand</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
<p><strong>Date Identified:</strong> -Jam</p>
|
||
|
||
<p><strong>Status Updates:</strong> 2025-11-12 00:00:00</p>
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">2 - High</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">In Progress</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">3 - Med</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Monitoring</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">4 - Low</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-secondary">Complete</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="vendor-section" data-vendor="Startup (Amazon)">
|
||
<div class="vendor-header">
|
||
<div class="vendor-name">Startup (Amazon)</div>
|
||
<div class="vendor-stats">
|
||
<div class="stat-item">
|
||
<div class="stat-value">1</div>
|
||
<div class="stat-label">Total</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #10b981;">0</div>
|
||
<div class="stat-label">Closed</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">0</div>
|
||
<div class="stat-label">Monitor</div>
|
||
</div>
|
||
<div class="stat-item">
|
||
<div class="stat-value" style="color: #f59e0b;">1</div>
|
||
<div class="stat-label">Incomplete</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="vendor-content">
|
||
<div class="status-tabs">
|
||
<button class="status-tab active" onclick="switchStatusTab(this, 'Startup (Amazon)')" data-status="all">All (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Startup (Amazon)')" data-status="updates_24h">Yesterday's Updates (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Startup (Amazon)')" data-status="oldest_unaddressed">Oldest Unaddressed (1)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Startup (Amazon)')" data-status="closed">Closed (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Startup (Amazon)')" data-status="monitor">Monitor (0)</button>
|
||
<button class="status-tab" onclick="switchStatusTab(this, 'Startup (Amazon)')" data-status="incomplete">Incomplete (1)</button>
|
||
</div>
|
||
|
||
<div class="status-tab-content active" data-status="all" data-vendor="Startup (Amazon)">
|
||
|
||
|
||
<div class="section">
|
||
<div class="section-title">High Priority (1 items)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam Clearing Equipment on Mezzanine</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Access issues at bypass inhibiting jam clear access for RME. Are all Cottermans installed?</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="updates_24h" data-vendor="Startup (Amazon)">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Yesterday's Updates</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No updates from yesterday</li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="oldest_unaddressed" data-vendor="Startup (Amazon)">
|
||
|
||
<div class="section">
|
||
<div class="section-title">Oldest 3 Unaddressed Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam Clearing Equipment on Mezzanine</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
<span class="age-days">30 days</span>
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Access issues at bypass inhibiting jam clear access for RME. Are all Cottermans installed?</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="closed" data-vendor="Startup (Amazon)">
|
||
<div class="section">
|
||
<div class="section-title">Closed Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No closed items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="monitor" data-vendor="Startup (Amazon)">
|
||
<div class="section">
|
||
<div class="section-title">Monitor Items (0)</div>
|
||
<ul class="item-list">
|
||
<li class="empty">No monitor items</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="status-tab-content" data-status="incomplete" data-vendor="Startup (Amazon)">
|
||
<div class="section">
|
||
<div class="section-title">Incomplete Items (1)</div>
|
||
<ul class="item-list">
|
||
|
||
<li>
|
||
<div class="item-header">
|
||
<div class="item-name">Jam Clearing Equipment on Mezzanine</div>
|
||
<div class="badges">
|
||
<span class="badge badge-warning">Incomplete</span>
|
||
<span class="badge badge-high">2 - High</span>
|
||
|
||
</div>
|
||
</div>
|
||
<div class="item-details">
|
||
<p class="item-description"><strong>Description:</strong> Access issues at bypass inhibiting jam clear access for RME. Are all Cottermans installed?</p>
|
||
<p><strong>Date Identified:</strong> 10/14/2025</p>
|
||
|
||
|
||
|
||
</div>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div class="footer">
|
||
<p>Report generated automatically from Excel punchlist data</p>
|
||
</div>
|
||
</div>
|
||
|
||
<script>
|
||
let currentVendorTab = 'all';
|
||
|
||
function switchVendorTab(vendorName) {
|
||
currentVendorTab = vendorName;
|
||
|
||
// Update tab buttons
|
||
document.querySelectorAll('#vendor-tabs .tab').forEach(tab => {
|
||
if (tab.dataset.vendor === vendorName) {
|
||
tab.classList.add('active');
|
||
} else {
|
||
tab.classList.remove('active');
|
||
}
|
||
});
|
||
|
||
// Show/hide vendor sections
|
||
document.querySelectorAll('.vendor-section').forEach(section => {
|
||
const sectionVendor = section.dataset.vendor;
|
||
if (vendorName === 'all' || sectionVendor === vendorName) {
|
||
section.style.display = '';
|
||
} else {
|
||
section.style.display = 'none';
|
||
}
|
||
});
|
||
|
||
// Reapply filters after switching tabs
|
||
applyFilters();
|
||
}
|
||
|
||
function applyFilters() {
|
||
const searchText = document.getElementById('search-input').value.toLowerCase();
|
||
const vendorFilter = document.getElementById('vendor-filter').value;
|
||
const statusFilter = document.getElementById('status-filter').value;
|
||
const priorityFilter = document.getElementById('priority-filter').value;
|
||
|
||
const vendorSections = document.querySelectorAll('.vendor-section');
|
||
let visibleCount = 0;
|
||
|
||
vendorSections.forEach(section => {
|
||
const vendorName = section.querySelector('.vendor-name').textContent.trim();
|
||
const items = section.querySelectorAll('.item-list li');
|
||
let hasVisibleItems = false;
|
||
|
||
// Check vendor tab (currentVendorTab)
|
||
if (currentVendorTab !== 'all' && vendorName !== currentVendorTab) {
|
||
section.style.display = 'none';
|
||
return;
|
||
}
|
||
|
||
// Check vendor filter
|
||
if (vendorFilter && vendorName !== vendorFilter) {
|
||
section.style.display = 'none';
|
||
return;
|
||
}
|
||
|
||
// Filter items within section
|
||
items.forEach(item => {
|
||
const itemName = item.querySelector('.item-name')?.textContent.toLowerCase() || '';
|
||
const itemDescription = item.querySelector('.item-description')?.textContent.toLowerCase() || '';
|
||
const itemDetails = item.querySelector('.item-details')?.textContent.toLowerCase() || '';
|
||
const itemText = (itemName + ' ' + itemDescription + ' ' + itemDetails).toLowerCase();
|
||
|
||
const statusBadge = item.querySelector('.badge-success, .badge-warning, .badge-danger');
|
||
const status = statusBadge ? statusBadge.textContent.trim() : '';
|
||
|
||
const priorityBadge = item.querySelector('.badge-critical, .badge-high, .badge-medium, .badge-low');
|
||
const priority = priorityBadge ? priorityBadge.textContent.toLowerCase() : '';
|
||
let priorityMatch = priorityFilter === '';
|
||
if (priorityFilter === 'critical' && (priority.includes('critical') || priority.includes('very high'))) {
|
||
priorityMatch = true;
|
||
} else if (priorityFilter === 'high' && priority.includes('high') && !priority.includes('very') && !priority.includes('critical')) {
|
||
priorityMatch = true;
|
||
} else if (priorityFilter === 'medium' && priority.includes('medium')) {
|
||
priorityMatch = true;
|
||
} else if (priorityFilter === 'low' && priority.includes('low')) {
|
||
priorityMatch = true;
|
||
}
|
||
|
||
const matchesSearch = !searchText || itemText.includes(searchText);
|
||
const matchesStatus = !statusFilter || status === statusFilter;
|
||
const matchesPriority = priorityMatch;
|
||
|
||
if (matchesSearch && matchesStatus && matchesPriority) {
|
||
item.style.display = '';
|
||
hasVisibleItems = true;
|
||
} else {
|
||
item.style.display = 'none';
|
||
}
|
||
});
|
||
|
||
// Show/hide empty sections
|
||
const visibleItems = section.querySelectorAll('.item-list li[style=""], .item-list li:not([style*="display: none"])');
|
||
if (visibleItems.length > 0 || (!searchText && !statusFilter && !priorityFilter)) {
|
||
section.style.display = '';
|
||
visibleCount++;
|
||
} else {
|
||
section.style.display = 'none';
|
||
}
|
||
});
|
||
|
||
// Update results count
|
||
document.getElementById('results-count').textContent =
|
||
`Showing ${visibleCount} vendor section(s) matching filters`;
|
||
}
|
||
|
||
function clearFilters() {
|
||
document.getElementById('search-input').value = '';
|
||
document.getElementById('vendor-filter').value = '';
|
||
document.getElementById('status-filter').value = '';
|
||
document.getElementById('priority-filter').value = '';
|
||
|
||
// Reset to "All Vendors" tab
|
||
switchVendorTab('all');
|
||
|
||
// Show all sections and items
|
||
document.querySelectorAll('.vendor-section').forEach(section => {
|
||
section.style.display = '';
|
||
});
|
||
|
||
document.querySelectorAll('.item-list li').forEach(item => {
|
||
item.style.display = '';
|
||
});
|
||
|
||
// Reset status tabs in each vendor section
|
||
document.querySelectorAll('.status-tab').forEach(tab => {
|
||
tab.classList.remove('active');
|
||
});
|
||
document.querySelectorAll('.status-tab-content').forEach(content => {
|
||
content.classList.remove('active');
|
||
});
|
||
|
||
// Activate "All" status tabs
|
||
document.querySelectorAll('.status-tab[data-status="all"]').forEach(tab => {
|
||
tab.classList.add('active');
|
||
});
|
||
document.querySelectorAll('.status-tab-content[data-status="all"]').forEach(content => {
|
||
content.classList.add('active');
|
||
});
|
||
|
||
document.getElementById('results-count').textContent = '';
|
||
}
|
||
|
||
// Apply filters on Enter key in search
|
||
document.addEventListener('DOMContentLoaded', function() {
|
||
document.getElementById('search-input').addEventListener('keypress', function(e) {
|
||
if (e.key === 'Enter') {
|
||
applyFilters();
|
||
}
|
||
});
|
||
|
||
// Auto-apply on filter change
|
||
document.getElementById('vendor-filter').addEventListener('change', applyFilters);
|
||
document.getElementById('status-filter').addEventListener('change', applyFilters);
|
||
document.getElementById('priority-filter').addEventListener('change', applyFilters);
|
||
});
|
||
|
||
function switchStatusTab(tabElement, vendorName) {
|
||
const status = tabElement.dataset.status;
|
||
|
||
// Update tabs for this vendor
|
||
const vendorSection = document.querySelector(`.vendor-section[data-vendor="${vendorName}"]`);
|
||
if (!vendorSection) return;
|
||
|
||
vendorSection.querySelectorAll('.status-tab').forEach(t => {
|
||
if (t.dataset.status === status) {
|
||
t.classList.add('active');
|
||
} else {
|
||
t.classList.remove('active');
|
||
}
|
||
});
|
||
|
||
// Update content for this vendor
|
||
vendorSection.querySelectorAll('.status-tab-content').forEach(content => {
|
||
if (content.dataset.status === status && content.dataset.vendor === vendorName) {
|
||
content.classList.add('active');
|
||
} else {
|
||
content.classList.remove('active');
|
||
}
|
||
});
|
||
}
|
||
|
||
function switchUpdateTab(tabElement, vendorNameSafe) {
|
||
const updateType = tabElement.dataset.updateType;
|
||
|
||
// Find the parent updates section
|
||
const updatesSection = tabElement.closest('.section');
|
||
if (!updatesSection) return;
|
||
|
||
// Update sub-tabs
|
||
updatesSection.querySelectorAll('.updates-sub-tabs .status-tab').forEach(t => {
|
||
if (t.dataset.updateType === updateType) {
|
||
t.classList.add('active');
|
||
} else {
|
||
t.classList.remove('active');
|
||
}
|
||
});
|
||
|
||
// Update content
|
||
updatesSection.querySelectorAll('.update-tab-content').forEach(content => {
|
||
if (content.dataset.updateType === updateType && content.dataset.vendorUpdate === vendorNameSafe) {
|
||
content.classList.add('active');
|
||
} else {
|
||
content.classList.remove('active');
|
||
}
|
||
});
|
||
}
|
||
|
||
function showOnly24hUpdates() {
|
||
// Remove active class from all quick filter buttons
|
||
document.querySelectorAll('.quick-filter-btn').forEach(btn => {
|
||
btn.classList.remove('active');
|
||
});
|
||
document.getElementById('filter-24h-updates').classList.add('active');
|
||
|
||
// Show only vendors with 24h updates, and switch to updates tab
|
||
let visibleCount = 0;
|
||
document.querySelectorAll('.vendor-section').forEach(section => {
|
||
const vendorName = section.dataset.vendor;
|
||
const updates24hTab = section.querySelector('.status-tab[data-status="updates_24h"]');
|
||
|
||
if (updates24hTab) {
|
||
// Check the tab text for count - format is "Yesterday's Updates (X)"
|
||
const tabText = updates24hTab.textContent.trim();
|
||
const match = tabText.match(/\((\d+)\)/);
|
||
const count = match ? parseInt(match[1]) : 0;
|
||
|
||
if (count > 0) {
|
||
section.style.display = '';
|
||
visibleCount++;
|
||
|
||
// Switch to updates_24h tab for this vendor
|
||
switchStatusTab(updates24hTab, vendorName);
|
||
|
||
// Hide all other tab content except updates_24h
|
||
section.querySelectorAll('.status-tab-content').forEach(content => {
|
||
if (content.dataset.status === 'updates_24h' && content.dataset.vendor === vendorName) {
|
||
content.classList.add('active');
|
||
} else {
|
||
content.classList.remove('active');
|
||
}
|
||
});
|
||
|
||
// Find the updates section and activate the correct sub-tab
|
||
const updates24hContent = section.querySelector('.status-tab-content[data-status="updates_24h"][data-vendor="' + vendorName + '"]');
|
||
if (updates24hContent) {
|
||
const updatesSection = updates24hContent.querySelector('.section');
|
||
if (updatesSection) {
|
||
const subTabs = updatesSection.querySelectorAll('.updates-sub-tabs .status-tab');
|
||
// Priority order: Added > Closed > Monitor
|
||
const priorityOrder = ['added', 'closed', 'monitor'];
|
||
|
||
// Find the first sub-tab with items
|
||
for (const updateType of priorityOrder) {
|
||
const subTab = Array.from(subTabs).find(tab => tab.dataset.updateType === updateType);
|
||
if (subTab) {
|
||
const subTabText = subTab.textContent.trim();
|
||
const subTabMatch = subTabText.match(/\((\d+)\)/);
|
||
const subTabCount = subTabMatch ? parseInt(subTabMatch[1]) : 0;
|
||
|
||
if (subTabCount > 0) {
|
||
// Get vendor name safe for switchUpdateTab
|
||
const vendorNameSafe = vendorName.replace('/', '_').replace(' ', '_').replace('(', '').replace(')', '');
|
||
switchUpdateTab(subTab, vendorNameSafe);
|
||
break; // Found and activated, stop looking
|
||
}
|
||
}
|
||
}
|
||
}
|
||
}
|
||
} else {
|
||
section.style.display = 'none';
|
||
}
|
||
} else {
|
||
section.style.display = 'none';
|
||
}
|
||
});
|
||
|
||
// Update results count
|
||
document.getElementById('results-count').textContent =
|
||
`Showing yesterday's update items from ${visibleCount} vendor(s)`;
|
||
}
|
||
|
||
function showOnlyOldestUnaddressed() {
|
||
// Remove active class from all quick filter buttons
|
||
document.querySelectorAll('.quick-filter-btn').forEach(btn => {
|
||
btn.classList.remove('active');
|
||
});
|
||
document.getElementById('filter-oldest-unaddressed').classList.add('active');
|
||
|
||
// Switch to "All Vendors" tab first
|
||
switchVendorTab('all');
|
||
|
||
// Show only vendors with oldest unaddressed items, and switch to oldest tab
|
||
let visibleCount = 0;
|
||
document.querySelectorAll('.vendor-section').forEach(section => {
|
||
const vendorName = section.dataset.vendor;
|
||
const oldestTab = section.querySelector('.status-tab[data-status="oldest_unaddressed"]');
|
||
const oldestContent = section.querySelector('.status-tab-content[data-status="oldest_unaddressed"]');
|
||
|
||
if (oldestTab && oldestContent) {
|
||
// Check the tab text for count - format is "Oldest Unaddressed (X)"
|
||
const tabText = oldestTab.textContent.trim();
|
||
// Use a simpler regex pattern that works reliably
|
||
const match = tabText.match(/\((\d+)\)/);
|
||
const count = match ? parseInt(match[1]) : 0;
|
||
|
||
// Also check if there are actual items in the content
|
||
const items = oldestContent.querySelectorAll('.item-list li:not(.empty)');
|
||
const hasItems = items.length > 0;
|
||
|
||
if (count > 0 && hasItems) {
|
||
section.style.display = '';
|
||
visibleCount++;
|
||
|
||
// Switch to oldest_unaddressed tab for this vendor
|
||
switchStatusTab(oldestTab, vendorName);
|
||
|
||
// Hide all other tab content except oldest_unaddressed
|
||
section.querySelectorAll('.status-tab-content').forEach(content => {
|
||
if (content.dataset.status === 'oldest_unaddressed' && content.dataset.vendor === vendorName) {
|
||
content.classList.add('active');
|
||
} else {
|
||
content.classList.remove('active');
|
||
}
|
||
});
|
||
} else {
|
||
section.style.display = 'none';
|
||
}
|
||
} else {
|
||
section.style.display = 'none';
|
||
}
|
||
});
|
||
|
||
// Update results count
|
||
document.getElementById('results-count').textContent =
|
||
`Showing oldest unaddressed items from ${visibleCount} vendor(s)`;
|
||
}
|
||
|
||
function showAllVendors() {
|
||
// Remove active class from all quick filter buttons
|
||
document.querySelectorAll('.quick-filter-btn').forEach(btn => {
|
||
btn.classList.remove('active');
|
||
});
|
||
document.getElementById('filter-all-vendors').classList.add('active');
|
||
|
||
// Show all vendor sections
|
||
document.querySelectorAll('.vendor-section').forEach(section => {
|
||
section.style.display = '';
|
||
|
||
// Reset all tabs to "All" tab for each vendor
|
||
const vendorName = section.dataset.vendor;
|
||
const allTab = section.querySelector('.status-tab[data-status="all"]');
|
||
if (allTab) {
|
||
switchStatusTab(allTab, vendorName);
|
||
}
|
||
});
|
||
|
||
// Clear results count or reapply filters if any are set
|
||
const searchText = document.getElementById('search-input').value;
|
||
const vendorFilter = document.getElementById('vendor-filter').value;
|
||
const statusFilter = document.getElementById('status-filter').value;
|
||
const priorityFilter = document.getElementById('priority-filter').value;
|
||
|
||
if (searchText || vendorFilter || statusFilter || priorityFilter) {
|
||
applyFilters();
|
||
} else {
|
||
document.getElementById('results-count').textContent = '';
|
||
}
|
||
}
|
||
</script>
|
||
</body>
|
||
</html> |