SCOR Model -- Deliver Process Reference Model
Why does this standard matter?
The Deliver process of the SCOR (Supply Chain Operations Reference) model standardizes the entire process of delivering products to customers. When collaborating with overseas customers or global logistics partners, a SCOR-based transportation process serves as a common language for explaining service levels. Performance measurement metrics also follow SCOR criteria, enabling immediate benchmarking with global logistics companies.
How is it applied in VEXPLOR?
| SCOR Deliver Process | What it means for your operations | VEXPLOR approach |
|---|
| D1 (Stocked Product Delivery) | Standard delivery process from finished goods warehouse to customer | Fully implemented: shipment registration - dispatch - tracking - POD |
| D2 (Make-to-Order Delivery) | Delivery tracking for products manufactured per customer order | MTO order transportation tracking via ERP sales_order_items integration |
| D3 (Engineer-to-Order Delivery) | Project-type deliveries starting from design require complex schedule management | Basic tracking available; project logistics-specific features planned for future expansion |
| D4 (Retail/Distribution Delivery) | B2C or distribution channel deliveries require time windows and frequency management | Fully implemented: last-mile delivery hubs, time windows, re-delivery logic |
| DR (Return Delivery) | Return logistics requires the same traceability in the reverse direction | Fully implemented: return transportation process, SCM reverse logistics integration |
EDI -- Electronic Data Interchange Standard
Why does this standard matter?
EDI (Electronic Data Interchange) is an international specification for exchanging data between carriers and shippers through standardized electronic documents. Following EDI standards for dispatch requests, shipment status reception, and freight settlement with carriers reduces manual communication and improves data accuracy. Especially when using multiple carriers, a unified data format significantly improves operational efficiency.
How is it applied in VEXPLOR?
| EDI Standard | What it means for your operations | VEXPLOR approach |
|---|
| EDI 204 (Motor Carrier Load Tender) | Electronically transmits cargo information and dispatch requests to carriers | Data structure mapped via dispatch_orders + loading_plans tables |
| EDI 214 (Shipment Status) | Receives current shipment location and status in standard format | Tracked via delivery_tracking 8-stage status ENUM |
| EDI 990 (Response to Load Tender) | Electronically confirms carrier acceptance/rejection | Managed via dispatch_orders.status (planned-confirmed-cancelled) |
| EDI 210 (Freight Invoice) | Electronically receives carrier freight invoices for automatic reconciliation | Mapped via freight_calculations + settlement tables |
| EDI 856 (Ship Notice) | Pre-notifies trading partners of shipment information | Integrated via shipments + WMS outbound_orders |
Actual EDI message (EDIFACT/X12) conversion is handled at the Integration layer, while the data structures themselves maintain alignment with EDI standards for streamlined integration.
ISO 28000 -- Supply Chain Security Management Standard
Why does this standard matter?
ISO 28000 is an international standard for systematically managing security risks across the entire supply chain. It provides a framework for preventing security incidents and responding rapidly when they occur during hazmat transportation, high-value cargo transport, and international logistics. Global customers increasingly check ISO 28000 compliance when evaluating logistics partners' security levels.
How is it applied in VEXPLOR?
| ISO 28000 Requirement | What it means for your operations | VEXPLOR approach |
|---|
| Risk Assessment | Hazmat transportation and high-risk segments must be proactively identified and managed | hazmat_shipments (UN number/ADR class), claim_predictions (AI proactive prediction) |
| Security Management | Transportation security systems and access controls must be documented | Security cross-solution integration, compliance_records for security record management |
| Emergency Response | Rapid response systems and contact networks must be in place for hazmat incidents | hazmat_incidents incident management, emergency_contact, WF8 hazmat response workflow |
| Traceability | Cargo movement routes and status must be trackable in real time | GPS real-time tracking, blockchain POD (SHA-256 hash + electronic signature tamper-proofing) |
| Document Management | Security-related documents and certifications must be systematically maintained | compliance_records (file attachment), 4 document_template types |
GS1 EPCIS -- Electronic Product Code Event Tracking Standard
Why does this standard matter?
GS1 EPCIS (Electronic Product Code Information Services) is a standard for recording events (identification, loading, dispatch, location changes) that occur as cargo moves through the supply chain in a standardized format. Following this standard provides end-to-end supply chain visibility and enables consistent tracking data sharing between trading partners.
How is it applied in VEXPLOR?
| EPCIS Event | What it means for your operations | VEXPLOR approach |
|---|
| ObjectEvent (Cargo Identification) | Individually identifies and records unique cargo and lot information | shipment_items (barcode), shipment_holds (lot_id) |
| AggregationEvent (Loading) | Records the point when cargo is loaded onto pallets/containers | loading_plans, consolidation_shipments |
| TransactionEvent (Dispatch) | Records dispatch orders and shipment creation timestamps | dispatch_orders, shipments |
| Visibility Event (Tracking) | Records real-time cargo location and status changes | delivery_tracking (GPS, 8-stage status), telematics_events |