Job Description

Wipro's dynamic approach to people, process and technology has made us an industry leader for decades. Since 2006, Wipro has helped organisations power their businesses with the cloud. Our professional services help enterprises move faster, rethink processes and transform the way their people work.

Job Description

We are looking for an experienced IBM Sterling Integration Architect to lead the discovery, assessment, target-state design and migration planning of a business-critical B2B/EDI and managed file transfer landscape.

You will establish visibility of the current Sterling estate, identify business and application dependencies, assess separation and transition implications, and contribute to the future integration platform strategy. You will also play a critical role in the subsequent JDE migration programme, ensuring that Sterling integrations connected to JDE and external business partners are identified, assessed, redesigned, migrated, tested and transitioned without disruption to critical business processes.

Key Responsibilities

• Act as the lead architecture authority for IBM Sterling and all ERP-related B2B, EDI and managed file transfer integrations.
• Lead discovery and assessment of the Sterling landscape, including interfaces, trading partners, business processes, integration patterns, configurations and operational dependencies.
• Establish and validate the end-to-end integration baseline by mapping JDE applications and business processes to Sterling interfaces, external partners, infrastructure, security and support services.
• Define the target-state and transition architecture for Sterling, covering B2B/EDI, managed file transfer, partner connectivity, coexistence and integration with wider middleware and cloud platforms.
• Assess the ERP migration impact on interfaces, endpoints, data structures, transformations, communication protocols, partner profiles, certificates, schedules, routing, reconciliation and operational support.
• Determine whether existing Sterling capabilities and interfaces should be retained, consolidated, modernised, rehosted, redesigned, migrated, replaced or retired.
• Define migration groupings, sequencing, transitional states and coexistence requirements based on business criticality, technical dependencies, partner readiness and operational risk.
• Establish architecture and non-functional requirements for availability, scalability, performance, security, compliance, observability, disaster recovery, auditability and supportability.
• Provide architecture assurance across detailed design, testing, partner validation, cutover, rollback, production readiness and hypercare planning.
• Facilitate senior stakeholder workshops and translate technical findings into clear architecture decisions, risks, recommendations, roadmaps and executive-level decision materials.