• Experience in working on an EDI Migration Project (preferably IBM Sterling B2B Integrator as the target platform).

• Experience in maintaining/implementing IBM Sterling B2B Integrator. Experience in most of the following EDI maps:

110, 204, 210, 211, 212, 214, 215, 219, 250, 300, 301, 304, 310, 315, 810, 816, 820, 824, 850, 855, 856, 860, 864, 945, 990, 997.

• Develop Mapping Requirement Specification Documents.
• Comprehend source EDI maps for reference during the new map development.
• Ability to perform thorough Unit Testing using a prescribed testing tool(s), test scripts, and test data.
• Participate in testing activity and promptly fix defects.
• Develop and maintain quality technical documentation.
• Review EDI Developer's code to ensure quality and adherence to standards.
• Coach and direct EDI Developers.
• Understand the EDI solution architecture 'big picture' to help deliver the end-to-end solution.
• Contribute to Go Live Planning and Go Live support.
• Provide post-Go-Live Support.
• Provide Knowledge Transfer to customer.
• Comply with DivIHN Standards - CMMI, ISO, etc.
• 3+ years of EDI work experience.
• Ability to work on multiple "proof of concept" and assessments to identify the Migration Process and Project Technical Risks.
• R&D skills to create SDLC tools, utilities, templates, simulators, etc. to reduce the migration project execution risk.
• Must know Kubernetes, containers, and AWS cloud hosting.
• Learn a custom software add-on that accompanies IBM software (Eliassen.com).

Various projects the person will be responsible for:

• Create a "sandbox" EDI environment for independent work (not to interfere with client's active EDI environments.
• Define inventory of the baseline EDI work items and objects and copy the inventory to prepare a "pseudo working" EDI environment.
  • i.e. the env will be 'operational' however, it will not transact any real business transactions. An emulated environment that can be wiped clean and rebuilt repeatedly.

• Conduct various types of R&D projects, including but not limited to:
  • Study the entire "codebase" (EDI object inventory) to create migration strategies.
  • Analyze and categorize the migration patterns.
  • Research viability of AI-based automatic migration.
  • Create POCs for automated migration of EDI objects from source to target.
  • Create Trading Partner "test simulators" to help minimize the efforts required by real trading partners/customers when going live in the future.