Module implementation guides

Each module follows the common implementation backbone with the module-specific activities below.

A. Classification

Purpose: manage customs and export control classification across regulations, using manual classification, nomenclature browsing, decision trees, semi-automation, and workflow collaboration. The module is typically integrated with product introduction and ERP master data flows.

Step	Major implementation activities
1. Define product data model	Identify the article attributes needed for classification: product reference, description, composition, dimensions, material, supplier data, images, documents.
2. Configure nomenclatures & reference data	Activate relevant legal regulations, official nomenclatures, explanatory notes, and optional provider content (sourced by MyTower or from a content partner such as Mendel Verlag).
3. Configure views & workflows	Define classification status workflow and automation.
4. Configure roles & visibility	Define user roles and visibility (RBAC & CBAC).
5. Load initial catalog	Import existing codes, status, supporting documents, comments, BTI references, and historical classifications.
6. Build decision trees / rules (autoclassification)	Translate the customer's business decision trees into MyTower decision logic.

Key customer dependencies

• Knowledge and identification of material attributes required

• Readiness of business decision trees

B. Origin Management

Purpose: calculate, document, and distribute preferential and non-preferential origin across Free Trade Agreements, based on BOMs, component origin, HS codes, prices, rules of origin, and supplier declarations.

Step	Major implementation activities
1. Define required data	Map finished goods, BOMs, components, HS codes, prices, supplier origin, Made In, production location, and order data.
2. Configure FTA / ALE setup	Configure agreement groups, country groups, active FTAs, and calculation scope.
3. Configure ROO rules	Set up rules of origin by HS code, including value rules, weight rules, tariff shift rules, exceptions, and tolerances. Rules can also be sourced from a content partner such as Mendel Verlag.
4. Load initial origin data	Import existing supplier declarations, previous origin results, BOMs, component data, and customer declarations.
5. Configure supplier declaration process	Define DLT templates, supplier workflow, validity periods, electronic signature, reminders, and lifecycle statuses.
6. Configure origin calculation engine	Set calculation logic for finished goods, trading materials, BOM decomposition, best/worst-case simulations, and mass calculation.

Key customer dependencies

• Quality of master data

• Knowledge of origin calculation and strategy (e.g. recursive calculation or not)

C. Customs Procedure Management (aka Customs Tracker or Bonded Warehouse)

Purpose: receive ERP goods movements, apply business rules, manage customs-controlled stock, trigger procedures, reconcile stock, support e-globalization, and generate audit-ready traceability. The module is built as a configurable, context-driven platform where customer-specific logic is externalized into business rules and procedures.

Step	Major implementation activities
1. Scope customs procedures	Confirm regimes: bonded warehouse, inward processing, outward processing, temporary import, transit, returns, e-globalization.
2. Map operational movements	Identify ERP movement types, goods receipts, goods issues, transfers, production flows, sales flows, reversals, stock snapshots.
3. Define customs logic	Define how customs status, regime, consumption mode, duty-paid/unpaid status, and exceptions are determined.
4. Configure business rules	Configure rule criteria, validation checks, routing to error worklist, classification checks, lookup tables, and movement acceptance logic.
5. Configure procedures	Configure ingoing, outgoing, e-globalization, stock comparison, Customs Status Document or Customs Invoice generation, and any customer-specific customs procedures. (The procedure designer is planned to evolve with the end-2026 release.)
6. Configure stock model	Define warehouses, stock dimensions, batch logic, FIFO logic, customs status, valuation rules, transport cost logic.
7. Configure error worklist	Define user actions: correct, ignore, delete manual movement, resubmit, mass edit, and audit trail.

Key customer dependencies

• Knowledge of ERP transactions and customs impact

• Understanding of business rules and contribution to the creation

D. Customs Broker Management (post-filing)

Purpose: centralize broker declarations, map broker files to EU CDM/WCO data models, monitor declaration status, manage documents, control data quality, and measure broker performance. CBM can also integrate with Customs Tracker for e-globalization and bonded warehouse flows.

Step	Major implementation activities
1. Scope broker network	Identify brokers, countries, declaration types, entities, import/export/transit flows, and available broker report formats.
2. Define target data model	Confirm the minimum fields required for the specific customer context (declaration header, goods shipment, goods item, duties and taxes).
3. Contact broker and get reporting	Contact broker and get declaration reporting (can be done by customer). Verify compatibility of file and definition of report columns.
4. Configure brokers	Create broker IDs, linked entities, contacts.
5. Configure file mappings	Map each broker report format to the MyTower declaration model; configure static values, transformations, and lookup tables.
6. Configure declaration workflow	Define declaration statuses, closure rules, error statuses, amendment/re-submission process, and status synchronization.
7. Configure controls	Set mandatory field validation, format controls, ISO country checks, declaration consistency checks, and error codes.

Key customer dependencies

• Preparatory work from customer with brokers (can include contractualization to share data)

• Validation of global data model at the beginning

E. Sanctioned Parties Screening

Purpose: screen customers, suppliers, banks, vessels, intermediaries, and other entities against sanctions, PEP, adverse media, state-owned company, and other risk data sources. It covers ad hoc, list and transaction screening, fuzzy matching, release/block decisions, and ERP/TMS blocking logic.

Step	Major implementation activities
1. Scope screened populations	Confirm which parties are screened: customers, suppliers, carriers, banks, vessels, employees, intermediaries, end users.
2. Select data provider and lists	Confirm Dow Jones or other provider, sanctions lists, PEP, adverse media, UBO, SOC, country risk, trade compliance packages.
3. Define screening strategy	Decide ad hoc, batch/list screening, ongoing monitoring, transaction screening, frequency, and blocking logic.
4. Configure matching parameters	Configure fuzzy matching thresholds, country/gender/ID boosting, segmentation, false-positive management.
5. Configure workflows	Define open/cleared/confirmed/permanent clear/block statuses, reviewer roles, escalation, comments, audit evidence.
6. Integrate master data	Receive parties from ERP/CRM/TMS; send block/release decisions back to source systems.
7. Load and screen initial database	Load existing partner base and run initial screening; manage large false-positive backlog.
8. Test operational scenarios	New party creation, party update, list update, match resolution, ERP block/release, reporting.

Key customer dependencies

• Quality of master data

F. Transaction Screening / Export Control / License Management

Purpose: screen transactions against export control, embargo, license, end-use/end-user, US content, classification, origin, and company-specific rules. Transaction Screening checks commodities, origin/destination, exporter/consignee, end-use, end-user, US content, licenses, embargoes, and sanctions, with ERP/TMS blocking and screening audit history.

Step	Major implementation activities
1. Scope regulations and flows	Confirm export countries, destination countries, legal entities, product scope, transaction types, and regulations.
2. Define screening data model	Map ship-from, ship-to, sold-to, consignee, end-user, product, HS/ECCN, origin, US content, end-use, license attributes.
3. Configure regulatory rules	Set embargoes, license requirements, dual-use rules, national rules, company blacklists, and special restrictions.
4. Configure license repository	Load licenses, validity dates, values, quantities, countries, end-users, license conditions, statements, and documents.
5. Configure screening workflow	Define hold/release/block statuses, worklists, manual review, escalation, audit trail, and override rules.
6. Integrate transactional systems	Receive sales orders, deliveries, shipments, purchase flows, or TMS documents; return block/release decisions.
7. Integrate with Classification/Origin/SPS	Classification provides HS/ECCN; Origin may provide country or US content; SPS checks transaction parties.

Key customer dependencies

• Understanding of regulation to be implemented and parameter to be setup in the system

G. GTM Analytics

Purpose: provide Power BI-based KPIs and reporting across modules: classification performance, origin status, customs declarations, broker quality, duties, licenses, blocked transactions, and screening performance.

Step	Major implementation activities
1. Define KPI scope	Agree management KPIs, operational KPIs, audit KPIs, and reporting frequency.
2. Identify source modules	Classification, Origin, CBM, Customs Tracker, SPS, Transaction Screening, Compliance Tracker.
3. Configure data extraction	Set adapters, datasets, refresh frequency, security, and data history.
4. Implement dashboards	Implement standard dashboards and customer-specific reports (where in scope).
5. Validate data reconciliation	Compare BI figures with module screens, ERP data, broker reports, and customs reports.
6. Configure access rights	Role-based dashboard access by entity, market, region, and module.

Analytics can be delivered in several ways (agreed during scoping):

• Option 1: copy of the data in the BI database, collected by the customer

• Option 2: copy of the data in the BI database, with Power BI reports (PBIX) hosted in the MyTower tenant

• Option 3: copy of the data in the BI database, with Power BI reports (PBIX) hosted in the customer tenant