Business Analyst, EDI & Integration

Responsibilities

A. During rollout (implementation)

1. Analysis and requirements

· Identify all integration requirements of each office, covering EDI and API integrations with trading partners and integrations with internal systems, including the message types and interfaces involved, through discussions with business users and SMEs.

· Conduct fit-gap analysis against the standard message set and interfaces, and promote adoption of standard mappings over partner- or office-specific customisation wherever possible.

· Work closely with SMEs to gather requirements and prepare integration requirements documents covering message types, data flows, business rules, partner requirements and acceptance criteria.

2. CR management

· Own all integration-related CRs raised during the implementation and ensure that each adheres to the CR lifecycle, encompassing request, impact assessment, approval, build, testing and deployment.

· Review vendor effort estimates and quotations for each CR, and include cost, benefit and system impact in the CR impact assessment.

· Prepare CRs for prioritisation by the Product System Manager and SMEs, and obtain all required approvals at each stage of the CR lifecycle.

· Work closely with the rollout Project Manager, who tracks all rollout activities, and provide timely updates on CR status, issues and risks.

3. Solution and build

· Liaise with the vendor on interface and mapping specifications, ensuring they meet the stated requirements and that gaps and open issues are resolved.

· Coordinate with trading partners, including principals, ports, depots and third-party booking platforms, and with owners of in-house applications on message specifications, connectivity and implementation timelines.

4. Testing

· Own and perform thorough testing of all EDI functions in LinerX prior to UAT, covering inbound and outbound messages, mappings, data updates within the system, acknowledgements and error handling, and verify that each message and interface meets the requirements before release to SMEs.

· Plan and conduct UAT and end-to-end testing with SMEs and trading partners, including the preparation of test scenarios and test cases, coordination of test execution and recording of results.

· Lead the rectification of issues and defects identified during testing with the vendor and trading partners, through to resolution and retesting.

· Confirm that testing has been completed and formally signed off before changes are released.

5. Go-live and hypercare

· Be responsible for integration setup prior to go-live, including partner profiles, code mappings and connectivity configuration.

· Coordinate cutover activities with trading partners and in-house application owners.

· Prepare and update integration documentation, including interface and mapping specifications and partner lists, and brief SMEs and L2 support on the changes.

· Manage the rectification of EDI and integration issues with the vendor and trading partners during the hypercare period, until the site is formally handed over to BAU support.

B. BAU (post go-live)

1. CR intake and assessment

· Own all integration-related CRs raised after go-live from intake to closure, including requests to onboard new trading partners and message types, ensuring that each adheres to the CR lifecycle.

· Assess incoming CRs with business users, and work closely with SMEs to analyse requirements and prepare integration requirements documents.

· Review vendor effort estimates and quotations for each CR, and include cost, benefit and system impact in the CR impact assessment.

· Prepare CRs for prioritisation by the Change Board.

2. Solution, build and testing

· Liaise with the vendor on interface and mapping specifications, and coordinate with trading partners and in-house application owners on implementation.

· Own and perform thorough testing of the EDI functions in LinerX for every CR, plan and conduct end-to-end testing with SMEs and trading partners, and manage the rectification of defects through to resolution.

3. Release and handover

· Assess the readiness of each CR based on test results, approvals and business readiness, and provide a go/no-go recommendation to the Product System Manager.

· Update integration documentation for each delivered CR, and brief SMEs and L2 support on the changes.

· Lead the transition of delivered CRs into BAU, working with L2 support to hand over documentation, partner details and known issues.

4. CR governance

· Maintain the BAU integration CR register, including status, approvals and supporting documentation for each change.

· Maintain an up-to-date inventory of trading partners, message types and interfaces.

· Report on BAU CR progress, risks and issues to the Product System Manager.

5. Continuous improvement

· Engage regularly with the BAU support team to review recurring EDI and integration tickets, and propose improvements to address root causes and improve reliability.

· Proactively identify and propose improvements to integrations, including opportunities to standardise or automate data exchange.

· Keep abreast of developments in EDI, APIs and industry data standards, and assess their potential application to LinerX.

· Work closely with the Transformation team to identify and evaluate potential AI-driven improvements to LinerX integrations.

C. Across both phases

· Continuously reach out to principals, ports, depots and third-party booking platforms to establish and expand integrations with LinerX, identifying partners not yet integrated and driving them through onboarding.

· Collaborate with the Functions Business Analyst to ensure that functional changes and integrations are aligned.