90-Day TMS–WMS–ERP Integration Roadmap with Canonical Data Model
N.B. Upload a project list (ID, cash flows by period, capex/opex split, dependencies, headcount needs) and risk parameters (volatility, correlation if available). If a dependency chain is infeasible within [FiscalYear], flag with remediation options.
📄 Prompt Template
Create a 90-day integration roadmap connecting [TMSVendor], [WMSName], and [ERPName] via [APIScope] APIs/EDI with [Carriers]. Inventory current messages (e.g., 940/945, 204/214, 210, 856), identify duplicates, and define a canonical shipment/order entity (IDs, status taxonomy, timestamps, units, Incoterms). Specify sequencing for events (gate-in, unload start, pick complete, BOL issued, POD captured) and reconcile clocks/time zones. Include cut-over strategy, rollback criteria, and data quality rules (uniqueness, completeness, timeliness).
Output format: 1) Integration inventory table (Flow, Source, Target, Protocol, Frequency). 2) Canonical data dictionary (Field, Type, Required, Source of Truth). 3) Sequence diagram (steps with producer/consumer). 4) Dependency Gantt (Milestone, Owner, Start/Finish, Predecessor). 5) Non-functional requirements list (latency, availability, monitoring). 6) Acceptance test suite (Test, Input, Expected Output).