Implementation methodology
MyTower GTM modules are modular and can be implemented individually or combined in a roadmap; they usually integrate with ERP, TMS, WMS, customs systems, brokers, and trade content sources.
| Phase | Objective | Typical activities |
|---|---|---|
| 1. Scope & Fit-Gap | Confirm business scope and target countries/entities/processes | Process workshops, legal scope, system landscape, data sources, current pain points, target users |
| 2. Business Blueprint | Define target operating model and functional design | Future process, data model, roles, workflows, business rules, exception handling, reporting needs |
| 3. Integration Blueprint | Define inbound/outbound data flows | ERP/TMS/WMS interfaces, APIs/SFTP, mapping, frequency, ownership, error handling |
| 4. Configuration & Build | Configure the module and build required mappings/rules | Roles, views, statuses, business rules, reference data, workflows, interfaces |
| 5. Data Migration / Initial Load | Load starting data into MyTower | Products, partners, declarations, historical data, BOMs, supplier data, stock, licenses, documents |
| 6. SIT / Integration Testing | Validate technical and functional end-to-end flows | Interface tests, rule execution, status updates, error scenarios, regression checks |
| 7. Training & Change | Prepare operational teams | Key-user training, SOPs, work instructions, role-based training, broker/supplier onboarding |
| 8. UAT | Let business users validate real-life scenarios | Business test scripts, edge cases, user feedback, corrections, sign-off |
| 9. Cutover & Go-Live | Move from project to production | Data freeze/load, activation of interfaces, user access, first transactions, monitoring |
| 10. Hypercare & Run | Stabilize and transition to support | Daily checks, issue triage, KPI monitoring, backlog, handover to support/managed services |
Module-specific activities and customer dependencies are described in Module implementation guides.