SLAM Operations Service - Business Capabilities
Overview
The SLAM (Scan, Label, Apply, Manifest) Operations Service manages the final quality gate before packages are handed off to transportation carriers. It processes all packages regardless of which path they came from.
Business Capabilities
1. Package Scanning
Purpose: Verify package identity through barcode scanning.
| Capability |
Description |
| Barcode Verification |
Scan and verify package barcode |
| Order Matching |
Match package to order |
| Duplicate Detection |
Prevent duplicate processing |
| Scan Rate Monitoring |
Track scanning throughput |
2. Weight Verification
Purpose: Validate package weight against expected values.
| Capability |
Description |
| ACW Check |
Actual Check Weight verification |
| Variance Calculation |
Calculate weight variance |
| Tolerance Enforcement |
Apply variance thresholds |
| Exception Routing |
Route discrepancies to problem solve |
Weight Verification Rules
| Outcome |
Variance |
Action |
| PASS |
≤ 10% |
Continue to label |
| FLAG |
10-25% |
Manager review |
| FAIL |
> 25% |
Divert to problem solve |
flowchart TD
A[Weigh Package] --> B{Variance Check}
B -->|≤10%| C[PASS - Continue]
B -->|10-25%| D[FLAG - Manager Review]
B -->|>25%| E[FAIL - Problem Solve]
D -->|Approved| C
D -->|Rejected| E
3. Carrier Selection
Purpose: Select optimal carrier and service level.
| Capability |
Description |
| Rate Shopping |
Compare carrier rates |
| Service Matching |
Match service to SLA requirements |
| Zone Optimization |
Consider delivery zones |
| Override Handling |
Handle customer carrier preferences |
4. Label Generation
Purpose: Generate shipping labels with tracking information.
| Capability |
Description |
| Tracking Assignment |
Obtain tracking numbers from carriers |
| Label Formatting |
Format labels per carrier requirements |
| Routing Codes |
Generate sortation routing codes |
| Multi-Piece Support |
Handle multi-piece shipments |
Label Generation Workflow
sequenceDiagram
participant SLAM as SLAM Service
participant CARRIER as Carrier API
participant PRINTER as Label Printer
SLAM->>CARRIER: Request tracking number
CARRIER-->>SLAM: Tracking: 1Z999...
SLAM->>SLAM: Generate label content
SLAM->>PRINTER: Print label
PRINTER-->>SLAM: Print confirmed
5. Label Application
Purpose: Apply and verify label placement.
| Capability |
Description |
| Application Verification |
Confirm label applied |
| Position Validation |
Verify label position |
| Scan Confirmation |
Re-scan to confirm |
| Retry Handling |
Handle application failures |
6. Manifest Recording
Purpose: Record packages to carrier manifests.
| Capability |
Description |
| Manifest Creation |
Create carrier manifests |
| Package Recording |
Add packages to manifests |
| Manifest Closure |
Close manifests for pickup |
| Count Verification |
Verify package counts |
7. Exception Handling
Purpose: Handle exceptions during SLAM processing.
| Capability |
Description |
| Weight Exceptions |
Handle weight discrepancies |
| Label Failures |
Handle print/apply failures |
| Carrier Rejections |
Handle carrier API failures |
| Escalation Workflow |
Route to problem solve |
Exception States
stateDiagram-v2
[*] --> PROCESSING
PROCESSING --> WEIGHT_EXCEPTION: weight_fail
PROCESSING --> LABEL_EXCEPTION: label_fail
PROCESSING --> CARRIER_EXCEPTION: carrier_fail
WEIGHT_EXCEPTION --> RESOLVED: fixed
LABEL_EXCEPTION --> RESOLVED: fixed
CARRIER_EXCEPTION --> RESOLVED: fixed
WEIGHT_EXCEPTION --> DIVERTED: cannot_fix
LABEL_EXCEPTION --> DIVERTED: cannot_fix
CARRIER_EXCEPTION --> DIVERTED: cannot_fix
RESOLVED --> PROCESSING: retry
SLAM Session Workflow
sequenceDiagram
participant PATH as Path Services
participant SLAM as SLAM Session
participant SCALE as Scale
participant CARRIER as Carrier API
participant PRINTER as Printer
participant MANIFEST as Manifest
PATH->>SLAM: Pack Completed Event
SLAM->>SLAM: Create session
SLAM->>SCALE: Request weight
SCALE-->>SLAM: Actual weight
SLAM->>SLAM: Verify weight
SLAM->>CARRIER: Request label
CARRIER-->>SLAM: Tracking + routing
SLAM->>PRINTER: Print label
PRINTER-->>SLAM: Applied
SLAM->>MANIFEST: Add to manifest
SLAM-->>PATH: SLAMCompletedEvent
Integration Points
Upstream
| Source |
Events |
Purpose |
| Singles Path |
SinglesPackCompletedEvent |
Singles orders ready for SLAM |
| AFE Path |
RebinCompletedEvent |
AFE orders ready for SLAM |
| Batch Flow Path |
OrderConsolidatedEvent |
Batch orders ready for SLAM |
Downstream
| Target |
Events |
Purpose |
| Transportation |
SLAMCompletedEvent |
Package ready for shipping |
| Order Management |
SLAMCompletedEvent |
Order status update |
| Monitoring |
WeightDiscrepancyEvent |
Exception alerting |
| Monitoring |
SLAMExceptionEvent |
Exception alerting |
| KPI |
Target |
Description |
| SLAM Cycle Time |
< 30 sec |
Time per package through SLAM |
| Pass Rate |
> 98% |
Packages passing first attempt |
| Weight Accuracy |
> 99% |
Packages within weight tolerance |
| Label Quality |
> 99.5% |
Labels printed/applied correctly |
| Throughput |
600-800 UPH |
Units per hour per station |
Technology Stack
| Component |
Technology |
| Language |
Java 21 |
| Framework |
Spring Boot 3.3.3 |
| Database |
MongoDB 7.0 |
| Messaging |
Apache Kafka 7.5.0 |
| Port |
8086 |
References