ZTABS modernizes legacy applications for Munich enterprises in automotive, insurance, manufacturing and technology. Munich automotive companies operate SAP R/3 with thousands of custom Z-programmes and complex MES integration. Insurance carriers run legacy policy administration serving German and European markets. Industrial manufacturers operate legacy ERP and MES systems. ZTABS is remote-first by design from our Houston, Texas office.
Munich legacy modernization demand spans automotive SAP R/3 to S/4HANA migration with JIT/JIS production, insurance platform modernization for BaFin-supervised entities, industrial manufacturing system upgrades and technology platform decomposition.
Legacy app modernization in Munich at a glance
| Need | What we build | Key requirement |
|---|
| Automotive | SAP S/4HANA with MES | IEC 62443, Catena-X |
| Insurance | Platform modernization | BaFin, Solvency II, DORA |
| Manufacturing | ERP and MES upgrades | Industry 4.0, IoT |
| Defence | Platform modernization | Actual controlled item, data, US nexus |
| Technology | Platform decomposition | GDPR, BDSG |
Automotive SAP R/3 to S/4HANA migration
Munich automotive OEMs and Tier 1 suppliers operate SAP R/3 systems with thousands of custom Z-programmes, BAPIs and user exits accumulated over decades. MES systems integrate tightly with SAP for production scheduling, quality management and plant maintenance.
Custom ABAP analysis. Thousands of Z-programmes, enhancement implementations and custom BAPIs analysed for S/4HANA compatibility. Simplification database assessment. Business process mapping for HANA-optimised replacement.
JIT and JIS production. Just-in-time and just-in-sequence production scheduling tightly coupled between SAP and MES systems. Legacy JIT/JIS integration preserved and modernized for real-time responsiveness. Supplier EDI connections for call-off schedules maintained.
Quality management. SAP QM with MES quality inspection integration modernized. Statistical process control, measurement data capture and supplier quality scoring preserved.
Plant maintenance. SAP PM with MES condition monitoring integration modernized. Predictive maintenance enabled through IoT sensor data integration.
Catena-X. Membership distinct from operational data-space access. Eclipse Dataspace Connector integration for specific use cases. Digital product passport, supply chain traceability and demand-capacity management. Not all modernized systems need Catena-X.
Modernizing Munich automotive or insurance systems?
Tell us about your SAP R/3 landscape, Z-programme volume and MES integration requirements. We start with assessment covering custom code analysis, MES mapping and S/4HANA migration strategy.
Insurance platform modernization
Munich insurers and reinsurers operate legacy policy administration, claims and actuarial systems. Munich Re provides sector context for global reinsurance operations but is not claimed as a ZTABS client.
Policy administration. Life, health, auto and P&C insurance policy lifecycle modernized. Actuarial calculations preserved. BaFin Solvency II reporting dependencies maintained. German mandatory insurance requirements preserved.
Claims processing. Claims workflow modernized for digital submission, automated assessment and faster settlement. German-specific auto insurance and health insurance claims requirements preserved.
Reinsurance. Reinsurance treaty administration, facultative placements, cession calculations and recovery processing modernized for global reinsurance operations. Treaty accounting and BaFin regulatory reporting addressed.
DORA. Actual regulated institution ICT-contract requirements. Operational resilience testing, incident reporting and third-party risk management addressed in modernized architecture.
Industrial manufacturing modernization
Munich manufacturers operate legacy ERP and MES systems across global production networks.
SAP migration. Legacy SAP R/3 with German customisation for HGB accounting, German payroll, social security contributions and Finanzamt reporting migrated to current versions.
MES modernization. Manufacturing execution systems modernized for Industry 4.0, IoT sensor integration, predictive maintenance and real-time quality analytics. Legacy SCADA and PLC integration preserved.
IEC 62443. IEC 62443 industrial cybersecurity distinct from ISO 26262 automotive functional safety, IATF 16949 quality management and ISO/SAE 21434 automotive cybersecurity. Each standard has different scope and assessment methodology. No modernization guarantees product certification.
German regulation for Munich
GDPR and BDSG. GDPR directly applicable with BDSG supplementary. Multiple actual processing bases available.
TDDDG and UWG. TDDDG covers terminal-device storage and access, distinct from UWG electronic marketing. UWG Section 7(3) actual sale own similar, no objection, opt-out at collection and each message. No universal double-opt-in statute.
Works council. Section 87(1)(6) co-determination for technical devices capable of monitoring employee behaviour or performance, with agreement or conciliation. Section 90 timely planning information and consultation. Section 111 applies to companies normally with more than 20 eligible employees for proposed operational changes that may cause substantial disadvantages; within Section 111, companies with more than 300 employees have adviser entitlement. Not every technology change or employee data use automatically requires the same approval. Early engagement during assessment reduces delay risk.
HGB and AO retention. Baseline 10 years books, 8 years vouchers, 6 years correspondence. KWG institutions including branches, VAG-supervised entities and securities institutions keep vouchers for 10 years. Calendar-year-end document-event clocks under Section 257(5).
GoBD. Z1 direct, Z2 indirect, Z3 machine-evaluable data provision.
E-invoicing. B2G EN16931 alternatives not XRechnung-only. B2B receipt versus phased issuance with actual dates, entity and transaction requirements.
DORA and BAIT. DORA for actual regulated institutions. VAIT, KAIT, ZAIT revoked January 2025. Residual BAIT for specific institutions until 31 December 2026.
Bavaria. No general statutory Bildungsurlaub.
Strangler fig for automotive systems
Seam selection. Automotive seams: production planning, quality management, plant maintenance, logistics, finance. Insurance seams: policy administration, claims, actuarial, reinsurance, regulatory reporting. Manufacturing seams: production, quality, supply chain, finance.
Single authoritative write. One system authoritative for each transaction type and period during coexistence. SAP production order authoritative during SAP migration. MES quality records authoritative for real-time inspection data. Insurance dual-write dangerous for BaFin regulatory reporting.
Reconciliation. Idempotency keys enforced by receiving side. Finite retries with DLQ. Unknown outcomes require reconciliation before replay, especially for production orders, JIT/JIS schedules, insurance premium settlements and supplier payments.
Data migration methodology
Automotive data. Material master, BOM, routing, production order, quality and plant maintenance data migrated with operational verification. Z-programme custom data structures analysed and mapped. Supplier master data and EDI configuration preserved.
Insurance data. Policy records, claims history, actuarial data, reinsurance treaties and regulatory reporting data migrated with actuarial verification.
Data type mapping. Types, nulls, time zones, currency, rounding, identifiers, encoding, history and crosswalks reconciled. German-specific: SAP material master numbers with plant-specific customisation, BaFin regulatory reporting fields, HGB account codes, German date and number formatting with comma decimal separators. EUR currency precision.
Cutover rehearsal. Observable acceptance with measurable RTO, RPO and latency targets. Automotive cutover timed for production schedule gaps, model year transitions or plant shutdowns. Insurance cutover timed for renewal cycles. MES cutover requires agreed plant windows, rehearsal and fallback with residual production risk documented.
Inventory and discovery
Munich enterprise modernization begins with complete inventory: applications, users, scheduled jobs, database procedures, reports, file and EDI dependencies, vendor contracts, supported versus end-of-life versions.
Business rules discovered with users through representative transaction analysis. Automotive rules validated against production specifications, OEM requirements and supplier agreements. Insurance rules validated against BaFin requirements and actuarial standards.
Illustrative Example
Hypothetical: Munich automotive manufacturer migrating SAP R/3 with 4000 Z-programmes and MES integration
A Munich automotive Tier 1 supplier operates SAP R/3 with approximately 4000 custom Z-programmes integrated with legacy MES across three production plants. JIT and JIS scheduling drives real-time production. Quality management integrates SAP QM with MES inspection stations. Plant maintenance uses SAP PM with condition monitoring from hundreds of IoT sensors.
Strangler fig migration would modernize MES integration layer first creating standardised APIs for production data exchange. Z-programmes analysed and categorised for HANA replacement, custom migration or retirement. JIT/JIS scheduling migrated per plant in agreed risk and dependency sequence. Quality and maintenance modernized in parallel with IoT platform upgrade.
Assumptions: SAP code accessible for analysis, production engineers available for rule validation, OEM scheduling requirements documented, and plant shutdowns available for cutover. Residual risks include undiscovered Z-programme dependencies, MES timing sensitivities for JIT/JIS, supplier EDI renegotiation, IEC 62443 assessment scope and works council engagement. No guarantee of specific OEE improvement, cost reduction or production capacity increase.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.
Integration and dependency management
Automotive integrations. OEM EDI connections for JIT/JIS schedules, supplier EDI for call-off and delivery, logistics provider connections, customs for export and Catena-X data-space.
Insurance integrations. BaFin regulatory reporting, GDV industry connections, reinsurance broker connections.
DATEV and proALPHA. Actual product version, vendor licence and tenant permissions. DATEV for tax advisory integration. proALPHA for Mittelstand manufacturing ERP where applicable.
Logs and retention
Logs minimise and redact secrets and regulated payloads with actual retention and legal holds. HGB 10 year baseline for accounting books. AO 8 year vouchers, 6 year correspondence. GoBD Z1, Z2, Z3 data provision requirements. IATF 16949 quality records per automotive customer retention requirements. Not all logs same retention period.
Assessment methodology
Application archaeology for Munich systems covers SAP custom ABAP analysis with simplification database, MES protocol analysis for JIT/JIS timing, insurance legacy platform analysis for business rule extraction and regulatory reporting analysis for BaFin compliance verification.
Regression and testing
Representative business-critical paths: automotive production order with JIT/JIS scheduling and quality inspection, insurance policy lifecycle with BaFin reporting, manufacturing production batch with IoT sensor data. Meaningful integration, performance and manual UAT with production engineering and actuarial approval.
Cost and timeline
Legacy system modernization follows the published cost guide.
| Tier | Range | Timeline | Example |
|---|
| UI Modernization | $40K to $100K | 8 to 16 weeks | New frontend, API wrapper, improved UX |
| Re-Platforming | $100K to $250K | 16 to 32 weeks | Modern stack, containerization, cloud, data migration |
| Re-Architecture | $250K to $400K | 8 to 14 months | Decompose monolith, event-driven, modern data layer |
| Full Rebuild | $400K to $500K+ | 12 to 18+ months | Ground-up rebuild, agreed availability target, rehearsed staged cutover |
Vendor comparison
Ranges are 2026 US-buyer guide-based estimates for re-platforming a 10 to 15 year old business-critical system using a strangler fig approach, modern stack, API wrappers, phased data migration and regression harness.
| Vendor type | Typical cost | Timeline |
|---|
| Freelance or dev collective | $40K to $130K | 5 to 12 months |
| Offshore systems integrator | $60K to $200K | 8 to 14 months |
| ZTABS | $100K to $280K | 6 to 12 months |
| Big 4 consultancy | $300K to $1M+ | 10 to 18 months |
| SaaS replacement vendor | $50K to $200K implementation | 4 to 9 months |
Parallel-running infrastructure, senior knowledge-transfer time and where applicable compliance revalidation can add a combined scope-dependent $100K to $500K+ planning allowance. The guide's examples are SOX, HIPAA and FDA; actual applicable regime depends on the engagement.
Proposal evaluation criteria
Evaluate any vendor proposal against these six criteria regardless of price tier.
| Criterion | What to verify |
|---|
| Strategy, deliverables and acceptance | Defined modernization phases with measurable acceptance criteria at each stage |
| Data source-of-truth and reconciliation | Which system is authoritative per object and period, agreed reconciliation tolerances and exception register |
| Rehearsal, cutover and rollback | Rehearsed cutover with RTO and RPO targets, documented rollback feasibility after schema and data changes |
| Security, privacy, compliance and approval scope | Applicable regulations identified with actual approval authority and scope |
| Full recurring costs | Licensing, parallel-run infrastructure, support, monitoring and decommission costs beyond initial build |
| Human roles and responsibilities | Provider and customer trainer-validator-support split, agreed working languages, translated materials review and on-site responsibilities where needed |
Need help modernizing Munich enterprise systems?
Share your legacy system landscape, SAP customisation scope and modernization constraints. We provide a scoped estimate based on system complexity.
How delivery works
ZTABS is remote-first by design from our Houston, Texas office. Overlap with Munich business hours for coordination and review.
When ZTABS is not the right fit
- The system still works and nobody is asking for changes. Wait for a real forcing function.
- SAP S/4HANA licencing and greenfield implementation. SAP licence selection, greenfield configuration and SAP partner-led implementation are the licensed vendor's and customer's scope. This engagement modernizes the surrounding integration, data migration and custom Z-programme conversion that connects to the new platform.
- On-site programme office and multi-vendor coordination. This engagement delivers application modernization. Separately contracted programme governance, on-site management and advisory retainers have different scope and responsibilities.
- On-site embedded team. ZTABS is remote-first by design. On-site staffing, training and support retainers for this engagement are separately agreed.
- BaFin or BfDI regulatory advisory. This engagement builds platforms, not regulatory advice. Regulatory advisory is separately engaged.
White-label AI products
ZTABS builds custom white-label AI products for clients to brand and resell. Munich technology companies can commission white-label AI platforms for distribution under their own brand.
Modernization approach selection
Munich enterprises need clear criteria for choosing between approaches.
Targeted remediation. Adding specific capabilities. Example: adding Catena-X data-space connector to existing SAP without full migration.
Re-platforming. Moving to modern infrastructure while preserving logic. Example: migrating legacy insurance billing to cloud while preserving actuarial algorithms.
Re-architecture. Decomposing monolith into services. Example: extracting quality management and plant maintenance from monolithic SAP as independent modern services.
Full rebuild. Ground-up development for systems where legacy code is unmaintainable. Example: replacing end-of-life custom MES with modern Industry 4.0 platform.
Data type mapping for Munich industries
Munich industry data has unique types requiring careful migration planning. Automotive: SAP material master numbers with plant-specific and OEM-specific codes, BOM structure identifiers with multi-level supplier references, production order numbers with JIT/JIS sequence identifiers, IATF 16949 quality inspection record identifiers. Insurance: BaFin regulatory reporting fields, reinsurance treaty identifiers, actuarial valuation dates. German date and number formatting with comma decimal separators.
Risks and mitigations
JIT/JIS production continuity. Production scheduling addressed at each migration phase with agreed plant windows, rehearsal and fallback procedures. Manufacturing PLC and MES writes need explicitly approved engineering authority, envelope, change controls, independent safety interlocks and validated failure mode. Residual production risk documented.
BaFin regulatory continuity. All regulatory reporting addressed at each migration phase. Material outsourcing notification where required.
Works council engagement. Works council co-determination requirements respected. Section 87 agreement or conciliation before technical monitoring changes.
Technology platform modernization
Munich technology companies operate legacy platforms requiring modernization for scale and European market access.
IoT platform modernization. Legacy industrial IoT platforms modernized for real-time sensor data processing, edge computing and cloud analytics.
Handover
Modernization handover includes runbooks, data lineage, licensing, support contacts and accountable owners. Automotive handover includes production system specifications, MES integration documentation, OEM EDI specifications and IATF 16949 quality documentation. Insurance handover includes BaFin compliance documentation, DORA resilience evidence and reinsurance documentation.
Ready to modernize your Munich legacy systems?
Share your legacy system landscape, SAP customisation scope and modernization constraints. We start with assessment covering application archaeology, compliance mapping and modernization strategy.