Project Incident Manager for Manhattan Active (MAWM/MAO) / Remote within Europe

๐Ÿข Kapres Technology, S.L. ยท all Kapres Technology, S.L. jobs
๐Ÿ“ France,Germany,Italy,Netherlands,Poland,Slovakia,Spain,Sweden
๐Ÿ“… Posted 2026-07-23 ยท via Himalayas
๐Ÿท Project-Incident-Manager,Incident-Management,IT-Project-Delivery,Supply-Chain-Technology,Warehouse-Management-Systems,Remote-Emergency-Services-Project-Manager
Apply on original site โ†—

At Kapres Technology, we are looking for an Project Incident Manager for Manhattan Active (MAWM/MAO) implementations to work with a multinational client, a leader in the logistics sector.

Looking for someone who can start at the latest by end of August and needs to be located in Western Europe due to scale of projects operating in EU Or Eastern/ Central North America.

A Project Incident Manager for Manhattan Active (MAWM/MAO) implementations, responsible for managing critical incidents that threaten project milestones, testing, cutover, hypercare, or go-live. The role acts as the central point of coordination across business, IT, Manhattan Associates, integration partners, and third-party vendors to restore service and minimize project impact.

Key Responsibilities

Incident Leadership

-
Lead the management of high-priority project incidents during design, build, testing, cutover, and hypercare.

-
Assess incident severity, business impact, and project risk.

-
Establish clear ownership and drive incidents through to resolution.

-
Chair incident bridge calls and ensure effective coordination across all teams.

-
Maintain accurate incident logs, actions, decisions, and timelines.

Technical Coordination

-
Coordinate technical teams across:

-
Manhattan Active Warehouse Management (MAWM)

- Manhattan Active Order Management (MAO)

-
Integration platforms (e.g. API, iPaaS, ESB)

- Customer Systems

- Transport Management Systems

- Carrier integrations

- WCS/WES automation systems

- Identity and infrastructure teams

-
Ensure root cause investigations are completed rather than simply implementing workarounds.

-
Coordinate defect prioritisation and deployment of fixes.

Stakeholder Communication

-
Provide regular executive updates during major incidents.

-
Translate technical issues into business impacts.

-
Communicate recovery plans, risks, and expected resolution times.

-
Manage communications with customers, business stakeholders, vendors, and programme leadership.

Project Delivery Support

-

Protect key project milestones including:

- SIT

- UAT

- Performance Testing

- Cutover

- Go-Live

- Hypercare

-
Escalate risks that could impact delivery dates.

-
Recommend contingency plans where required.

Governance

- Produce Major Incident Reports (MIRs).

-
Facilitate post-incident reviews and lessons learned.

-
Track recurring issues and identify systemic improvements.

-
Ensure incidents comply with programme governance and change management processes.

Vendor Management

-
Coordinate with:

- Manhattan Associates

- System Integrators

- Middleware providers

- Infrastructure partners

- Customer IT teams

-
Challenge vendors where necessary to meet agreed service levels and recovery commitments.

-
Escalate through vendor management channels when required.

Manhattan Active-Specific Responsibilities

A Project Incident Manager should understand the Manhattan Active ecosystem, including:

- MAWM configuration and workflows

- MAO order lifecycle

- SCI (Supply Chain Intelligence)

- Active Platform architecture

- API-first integration model

- Event framework

- Message processing

- Inventory synchronisation

- Order orchestration

- Wave management

- Picking, packing and shipping processes

- Inbound receiving

- Labour management

- Carrier integrations

- Manhattan Cloud deployments

- Release management

-
Configuration promotion between environments

Typical Major Incidents Managed

Examples include:

- Orders failing between MAO and MAWM

- Inventory synchronisation failures

- API failures

- Integration queue backlogs

- Authentication or OAuth failures

- Carrier label generation failures

- ASN processing failures

-
Performance degradation during load testing

- Warehouse RF device connectivity issues

- SCI reporting failures

- Cutover data migration issues

- Batch processing failures

- Failed production deployments

- Environment outages

- Customer-speci

โ† All remote jobs