arthur
9ce6ae37be
- Em dashes: 1712 remplaces par tirets simples (86 fichiers + _index.md, en-tete section Limagrain conserve) - Checklists: 24 '- [ ]' -> '- ☐' (3 pages operations, plus de todos Obsidian) - Ancres: 33 reparees (slugs GitHub + ancres HTML <a id> reconnues), 1 reciblee (manuel de reten) - related: tenseflow -> tense-flow, pie -> mechanical-elements, group.md retire (doublon shipping) - Registre: compteur global 122 -> 131 pages - Rapport racine _lint_report.md mis a jour (scan v2 + re-scan final: 0 anomalie) - Aucun fichier limagrain/ modifie (cloisonnement)
159 lines
7.8 KiB
Markdown
159 lines
7.8 KiB
Markdown
---
|
|
title: "Yard Management"
|
|
type: module
|
|
sources:
|
|
- areas/yard_management/index.md
|
|
- areas/yard_management/yard_appointments/index.md
|
|
- areas/yard_management/yard_appointments/yard_appointments.md
|
|
- areas/yard_management/yard_appointments/yard_checkpoints.md
|
|
- areas/yard_management/configuration/initial_configuration.md
|
|
- areas/yard_management/ERP.md
|
|
- areas/yard_management/notificationevents.md
|
|
- areas/yard_management/views/view_appointments.md
|
|
- areas/yard_management/views/configuration/view_yards.md
|
|
- areas/yard_management/views/configuration/view_vehicle_types.md
|
|
- areas/yard_management/views/configuration/view_commodity_types.md
|
|
- areas/yard_management/views/configuration/view_components.md
|
|
- areas/yard_management/views/configuration/view_dock_strategies.md
|
|
- areas/yard_management/views/configuration/view_routes.md
|
|
related:
|
|
- concepts/order-inbound.md
|
|
- concepts/order-outbound.md
|
|
- concepts/shipping.md
|
|
- concepts/reception.md
|
|
- concepts/stations.md
|
|
last_compiled: "2026-04-10"
|
|
---
|
|
|
|
# Yard Management
|
|
|
|
## Overview
|
|
|
|
The Yard Management System (YMS) module monitors and manages vehicle movements in the warehouse yard - from driver check-in through dock assignment to check-out. It provides dock scheduling capabilities that synchronize vehicle flows with warehouse inbound/outbound operations.
|
|
|
|
The module reduces wait times, eliminates bottlenecks, optimizes dock utilization, improves on-time performance, and provides security/access control for the yard.
|
|
|
|
## Key capabilities
|
|
|
|
- Appointment management: pre-scheduled vehicle slots with dock assignment strategies
|
|
- Check-in / check-out: checkpoint-based vehicle identification and tracking
|
|
- Dock assignment: rule-based automatic strategies (commodity type, vehicle type, time slot, proximity)
|
|
- Parking management: waiting area assignment while dock is not ready
|
|
- ERP/TMS integration: appointments can be created/modified via external messages
|
|
- Loan phone management: facility phones lent to drivers for in-yard communication (SMS)
|
|
- Vehicle weight control: scale integration at checkpoints
|
|
- Visual schedule: interactive calendar view of all dock appointments
|
|
- Auxiliary appointments: non-logistics events (maintenance, visits) in facility locations
|
|
|
|
## Architecture
|
|
|
|
### Yard components
|
|
A **yard** contains:
|
|
- **Warehouses**: served by the yard (one warehouse can only belong to one yard; all its docks managed through that yard)
|
|
- **Checkpoints**: entry/exit points where check-in/check-out is performed; each has a work mode (receiving/shipping/both)
|
|
- **Parking lots**: waiting areas for vehicles before dock assignment
|
|
- **Docks**: loading/unloading points (configured in EasyS); each dock has commodity type and vehicle type compatibility
|
|
- **Paths**: defined routes between yard components with distance values (used for dock assignment optimization)
|
|
|
|
### Appointment entity
|
|
|
|
**Core appointment attributes**:
|
|
|
|
| Field | Description |
|
|
|-------|-------------|
|
|
| Code | Appointment identifier |
|
|
| Status | Pending → Waiting → Pending dock decision → In process → Pending check-out → Finished / Canceled |
|
|
| Priority | Urgent / High / Normal / Low / Very low (affects dock assignment queue) |
|
|
| Type | Receiving (vehicle enters loaded), Shipping (vehicle enters empty), Auxiliary |
|
|
| Warehouse | Which warehouse the appointment serves |
|
|
| Yard | Which yard the vehicle enters |
|
|
| Planned receiving/shipping dates | Scheduled times |
|
|
| Real receiving/shipping dates | Actual times (auto-recorded by system) |
|
|
|
|
**Work order association**:
|
|
- **Receiving appointments**: must associate a receipt (status: Reception pending) or inbound order (Waiting/Reception pending/Receiving/Partially received)
|
|
- **Shipping appointments**: must associate a load (Open/Paused) or outbound order (Waiting/Released/Partially released/Pausing/Secured/Assigned)
|
|
|
|
**Vehicle attributes**:
|
|
- Carrier, plate number, vehicle type, driver(s), driver language (for SMS/notifications in driver's language)
|
|
- Maximum/receiving/shipping weight (for scale integration)
|
|
|
|
### Appointment status flow
|
|
|
|
```
|
|
Pending → Waiting (check-in done, in parking) → Pending dock decision (manual dock review)
|
|
→ In process (at dock, loading/unloading) → Pending check-out → Finished
|
|
Pending → Canceled
|
|
```
|
|
|
|
### Dock assignment strategies
|
|
Configurable rules combining:
|
|
- Commodity type compatibility
|
|
- Vehicle type compatibility
|
|
- Time slot availability
|
|
- Distance minimization (shortest path from default checkpoint to dock)
|
|
- Priority-based queue management for waiting vehicles
|
|
|
|
## Configuration
|
|
|
|
### Initial setup sequence
|
|
1. Define **yard** (link to all warehouses served)
|
|
2. Define **checkpoints** (entry/exit points; mark one as default)
|
|
3. Register **loan phones** (available for drivers; initial location = a checkpoint)
|
|
4. Define **parking lots** (waiting areas)
|
|
5. Define **vehicle types** (allowed in this yard)
|
|
6. Define **commodity types** (types of goods handled; dock compatibility)
|
|
7. Define **paths** between all yard components (distance values for optimization)
|
|
8. Configure **dock compatibility** per dock (commodity types + vehicle types)
|
|
9. Define **dock assignment strategies**
|
|
10. Define **facility locations and activities** (for auxiliary appointments)
|
|
|
|
**Note**: Docks are configured in EasyS or Easy Assistant; routes between yard elements must exist in the warehouse layout.
|
|
|
|
### ERP/TMS integration
|
|
Appointments can be created and modified via ERP or TMS communications. When a work order associated with an appointment is canceled (manually or via ERP), if the vehicle hasn't checked in yet, the appointment is automatically canceled.
|
|
|
|
## Operations
|
|
|
|
### Appointment creation
|
|
Manual creation via Appointments view (Yard menu). Required fields vary by appointment type:
|
|
- Receiving: carrier, vehicle, driver, planned dates, associated receipt or inbound order
|
|
- Shipping: carrier, vehicle, driver, planned dates, associated load or outbound order
|
|
- Auxiliary: facility location, activity type
|
|
|
|
### Check-in process
|
|
1. Vehicle arrives at checkpoint
|
|
2. Checkpoint user verifies vehicle plate and driver data
|
|
3. Weight recorded (if checkpoint has scale)
|
|
4. System assigns vehicle to available parking lot
|
|
5. When dock becomes available (via assignment strategy or manual decision): vehicle directed to dock
|
|
6. Appointment transitions to "In process"
|
|
7. Dock association updated automatically if rescheduled
|
|
|
|
### Check-out process
|
|
1. Loading/unloading operation completes (work order finished + vehicle preparation time elapses)
|
|
2. Appointment transitions to "Pending check-out"
|
|
3. Checkpoint user confirms vehicle exit
|
|
4. Exit weight recorded (if scale available)
|
|
5. Loan phone returned (if issued)
|
|
6. Appointment status: Finished
|
|
|
|
### Visual schedule
|
|
Interactive calendar showing all dock appointments, filtered by dock, date range, appointment type. Supports drag-and-drop rescheduling and visual conflict detection.
|
|
|
|
## Errors & troubleshooting
|
|
|
|
| Issue | Cause | Resolution |
|
|
|-------|-------|-----------|
|
|
| Cannot assign dock to appointment | Dock not compatible with appointment's commodity or vehicle type | Check dock compatibility configuration; add required compatibility |
|
|
| Vehicle outside allowed advance/delay window | Vehicle arrived too early or too late for check-in | Adjust allowed advance/delay time in yard configuration |
|
|
| Appointment auto-canceled | Work order canceled while vehicle not yet checked in | This is correct behavior; create new appointment if needed |
|
|
|
|
## Related
|
|
|
|
- [[order-inbound]] - Receiving appointments must be linked to receipt or inbound orders
|
|
- [[order-outbound]] - Shipping appointments must be linked to loads or outbound orders
|
|
- [[shipping]] - Loads and routes are the work order types for shipping appointments
|
|
- [[reception]] - Receipts are the work order types for receiving appointments
|
|
- [[stations]] - Docks are WMS station types; dock/stage configuration in Warehouse Designer
|