Assessment

Current-State Truth

Establishing the factual baseline across systems, ownership, and regional variation. End-to-end interactions, data flows, legacy constraints, and modernisation opportunities.

In progressUpdated 14 Mar 2026Capability Mapping →Risk Assessment →

Why this matters

No transformation decision is credible without a verified picture of what exists today. This page documents the systems, integrations, and constraints that any future-state must account for.

What this informs

Future-state scenario evaluation, deprecation sequencing, and the risk register. Every observation here maps to a decision or dependency.

What remains unresolved

System interaction map not yet validated with all domain stakeholders. Regional variation overlay incomplete for APAC.

Total Systems

Active

Legacy / Sunset

Domains Covered

Integration Hub

MuleSoft

System Inventory

Complete inventory of systems involved in after-sales operations. Status reflects current operational state — legacy systems are operational but targeted for replacement, sunset systems have confirmed decommission dates.

ID	System	Vendor	Domain	Region	Status	Dependencies	Decomm.
SYS-001	SAP ECC / S4HANA	SAP	Parts & Warranty	Global	active	SYS-003, SYS-005	—
SYS-002	Dealer Portal (Legacy)	Custom / Sitecore	Dealer Management	Global (excl. China)	legacy	SYS-001, SYS-003, SYS-004	—
SYS-003	Service Operations Platform	Siebel / Oracle	Service Operations	EMEA + Americas	legacy	SYS-001	2027-Q2
SYS-004	Telematics Gateway	Custom	Connected Vehicle	Global	active	—	—
SYS-005	DMS Integration Hub	MuleSoft	Integration	Global	active	SYS-001, SYS-002, SYS-003	—
SYS-006	China Dealer Platform	WeChat Mini Program + Custom	Dealer Management	China	active	—	—
SYS-007	BI & Reporting Platform	Power BI / Snowflake	Analytics	Global	active	SYS-001, SYS-003, SYS-004	—
SYS-008	Customer Experience Layer	Proposed	Customer Experience	Global	proposed	SYS-004, SYS-005	—

Architecture Observations

Tight coupling between Dealer Portal and backend systems

high

The Sitecore-based dealer portal has direct dependencies on SAP, Siebel, and MuleSoft. Any change in backend APIs requires portal redeployment. No abstraction layer.

No unified customer-facing digital experience

high

End customers have no self-service capabilities. All interactions mediated through dealer phone/email. Telematics data exists but is unused for customer communication.

China operates independently with no shared services

medium

WeChat Mini Program and local systems have zero integration with global platform. Business logic is duplicated. No shared domain model.

Analytics depend on ETL from multiple uncoordinated sources

medium

Power BI / Snowflake pulls from SAP, Siebel, and Telematics via separate ETL pipelines. No canonical data model. Data freshness varies from real-time to T+1.

Manual workarounds compensate for system gaps

high

Warranty claims adjudication, service cost estimation, and parts demand forecasting rely on manual processes and tribal knowledge. No automation or AI assistance.

MuleSoft integration hub is a single point of coordination

medium

All dealer-to-backend communication routes through MuleSoft. Well-architected but creates a dependency bottleneck. Any hub outage affects all dealer operations.

Architecture Diagrams

System Interaction Map

End-to-end data flows between all after-sales systems. Shows primary and secondary integration paths.

In progress

Architecture Lead

Regional Variation Overlay

How the architecture differs between Global, EMEA, Americas, APAC, and China deployments.

Draft

Regional Architect

Decision Layer

Decisions Supported

ADR-001 (strangler-fig), ADR-002 (domain boundaries), ADR-006 (SAP retention)

Dependencies

Feeds into DEL-002 (Future-State Scenarios) and DEL-005 (Risk Assessment). Blocks deprecation sequencing.

Next Actions

Complete system interaction map. Validate observations with domain stakeholders in Week 3 sessions.

Confidence

Medium — inventory complete, but interaction map and regional overlay require stakeholder validation.