spec.md 1.7 KB
ADDED Requirements
Requirement: Transport identity
The system SHALL assign transport records a transport number with fixed prefix SXYS and a monotonic sequence (example shape: SXYS0000001).
Scenario: Unique transport number
- WHEN two transport records are created concurrently
- THEN each SHALL receive a distinct transport number without collision
Requirement: Own fleet vs carrier vehicles
The system SHALL distinguish transport using company-owned vehicles versus transport-company vehicles and SHALL persist plate number, carrier company, and related vehicle master references as defined in vehicle management reference SQL.
Scenario: Carrier vehicle selected
- WHEN a dispatcher selects a vehicle belonging to a registered transport company
- THEN the transport record SHALL link to that company and vehicle metadata
Requirement: QR code for field and drivers
The system SHALL generate a QR code encoding sufficient information for drivers or on-site staff to open a secure workflow to view task context and submit transport documents and quantities.
Scenario: Specialist copies QR for driver
- WHEN plan specialist A requests QR for an active transport task
- THEN the system SHALL return a QR image or payload that validates to that transport instance
Requirement: Notify on-site for pending inbound/outbound
The system SHALL surface pending inbound/outbound tasks to on-site staff in sync with plan state (per integration milestone with mobile or H5 channels).
Scenario: Task visible when status is pending inbound
- WHEN a plan line reaches 待入库 per business rules
- THEN on-site worklist feeds SHALL include that task for configured staff roles