Arthur Ria
102 lines
4.7 KiB
Markdown
102 lines
4.7 KiB
Markdown
---
|
|
title: "Supply Chain Event Management (SCEM)"
|
|
type: module
|
|
sources:
|
|
- areas/supply_chain_event_management/index.md
|
|
- areas/supply_chain_event_management/notificationevents.md
|
|
- areas/supply_chain_event/index.md
|
|
- areas/supply_chain_analytics/index.md
|
|
related:
|
|
- modules/3pl-portal.md
|
|
- concepts/transactions.md
|
|
- concepts/erp-interface.md
|
|
last_compiled: "2026-04-10"
|
|
---
|
|
|
|
# Supply Chain Event Management (SCEM)
|
|
|
|
## Overview
|
|
|
|
The Supply Chain Event Management module provides a configurable, real-time event notification system for the warehouse. It monitors warehouse events and alerts users through alarms via email, SMS, or web interface notifications. Users control which events they receive, on what channels, and on what schedule.
|
|
|
|
The module is the notification infrastructure underpinning all Easy WMS modules — every notification event in AGV, Pallet Shuttle, Billing, Yard Management, and other modules is delivered through SCEM.
|
|
|
|
## Key capabilities
|
|
|
|
- Event subscription: users subscribe to specific notification events per warehouse
|
|
- Multi-channel delivery: web interface notification, email, SMS
|
|
- Schedule-based notification profiles: different channels for different days/times
|
|
- Delegated subscription: users can configure notifications on behalf of other users
|
|
- Automatic system reactions: some events trigger automated system responses
|
|
- Alarm monitoring: track outstanding alarms until resolved
|
|
- Event escalation: if no action taken, alarm escalates to next subscriber level
|
|
- Internal messaging: user-to-user internal messages through WMS interface
|
|
- 3PL client notifications: subscribe external 3PL client organization users to warehouse events
|
|
- Message language: notifications sent in the recipient's configured language (fallback: organization language)
|
|
|
|
## Architecture
|
|
|
|
### Core entities
|
|
|
|
**Notification event**: a defined event in the system (e.g., "AGV extraction error", "Billing generation error", "GNA import error"). Each module defines its own notification events.
|
|
|
|
**Notification group**: categorization of events (e.g., AGV, Communications, Billing). Users subscribe at the event level.
|
|
|
|
**Alarm**: an instance of a notification event that has been triggered. Tracked until resolved.
|
|
|
|
**Notification profile**: user-specific configuration of: event, channel (web/email/SMS), schedule (days of week, time ranges).
|
|
|
|
### ERP communication error notification (GNA)
|
|
|
|
The SCEM module includes a specific notification for ERP message processing failures:
|
|
|
|
| Code | Event |
|
|
|------|-------|
|
|
| `Notification_GNAImportError` | Error in exchange of information between ERP and WMS. Notifies warehouse, message type, error description, XML file generated, and date. |
|
|
|
|
Notification group: Communications. Can subscribe: SuperAdmin, Administrators, Managers.
|
|
|
|
### Subscription configuration options
|
|
|
|
| Mode | Description |
|
|
|------|-------------|
|
|
| Single subscription | User subscribes themselves to events and channels |
|
|
| Delegated subscription | User A configures notifications for User B (email/SMS channels only) |
|
|
| 3PL client subscription | Warehouse manager subscribes a 3PL client organization user to warehouse events |
|
|
|
|
## Configuration
|
|
|
|
### Notification profile setup
|
|
1. Go to Organization > Notification profiles
|
|
2. Select user and notification event
|
|
3. Choose channel(s): web notification, email, SMS
|
|
4. Set schedule: days and hours when each channel is active
|
|
5. Optional: set escalation targets if alarm not acknowledged within time limit
|
|
|
|
### Common configuration examples (from documentation)
|
|
- Subscribe to notifications and receive by email
|
|
- Subscribe to notifications and receive by SMS
|
|
- Subscribe a 3PL client organization's user to 3PL warehouse notifications
|
|
- Subscribe to notifications and receive on web
|
|
- Subscribe other users to receive notifications on web
|
|
- Notify simultaneously on web and email (always or by schedule)
|
|
- Filter notifications (select specific events from available set)
|
|
|
|
## Operations
|
|
|
|
### Alarm lifecycle
|
|
1. Event occurs in warehouse → alarm generated
|
|
2. Notification sent to subscribed users on their active channels
|
|
3. User acknowledges and resolves the underlying issue
|
|
4. Alarm marked as resolved
|
|
5. If no action taken within escalation window: alarm escalated to next level subscriber
|
|
|
|
### Internal messaging
|
|
Any Easy WMS user can send an internal message to another user. The recipient sees the message when they next log in. No channel configuration needed for internal messages.
|
|
|
|
## Related
|
|
|
|
- [[3pl-portal]] — 3PL client users can subscribe to SCEM notifications about their operations
|
|
- [[transactions]] — Transaction events (STK.ADJ, CON.MOVE, etc.) can trigger SCEM notifications
|
|
- [[erp-interface]] — GNA import errors (ERP communication failures) are notified via SCEM
|