BP-1156·v1.3Changes requested
Cross-Dock Planning — APAC
Planning · PacRim Retail · cross-dock, APAC
AS
Ana Souza
consultant
Compliance score
20/100
Blocking gaps
2
AI suggestions
33
Open issues
22
Section · configuration_arch
Configuration Architecture
Edited 1h ago by Priya Raman·81% complete
Blueprint BP-1156 vv1.3
├─ rule_set "release"
│ ├─ window: 36h
│ ├─ consolidation: enabled
│ └─ equipment_policy: $ref(cfg_05)
├─ reference_data
│ ├─ lane_groups: 42
│ └─ carriers: 18
├─ choreography
│ ├─ in.edi214 → normalize → publish
│ └─ out.api.shipment → enrich → emit
└─ governance
├─ approver_role: lead
└─ baseline_lock: false
Derived configurations (1)
- CFG-7855 · Cross-Dock Time WindowsTESTChanges requested
Requirement traceability
4 traced · 1 uncoveredReq ID
Requirement
Priority
Coverage
Source
REQ-OM-001
Multi-leg consolidation with 36h window across NA inbound flows
must
covered
Acme RFP §3.1
REQ-OM-002
Carrier capacity caps must respect contracted lane volume
must
covered
Acme RFP §3.2
REQ-OM-003
Equipment policy override per shipper account
should
partial
Workshop W3
REQ-OM-004
EDI 214 inbound normalization with event dedup
must
partial
Acme RFP §5.4
REQ-OM-005
Role-based field masking for PII on order detail
must
uncovered
Compliance Memo
REQ-OM-006
Demo dataset must cover EU peak-week pattern
should
partial
Workshop W5
REQ-OM-007
Cutover playbook with rollback within 4h RTO
must
covered
SOW Annex B
REQ-OM-008
Reuse pattern OM-STD-04 for consolidation engine
should
covered
Architect Review