Position: Permanent

Work environment: Onsite

Location: Winnipeg, Manitoba

Base Salary: Up to $90,000

Position Overview

Hammehr invites applications for the role of Business Systems Analyst, ERP Implementation on behalf of our client for a full time permanent opportunity.

Our client is a large North American manufacturer undertaking a multi-year ERP implementation across 11 plants. The program uses IFS and is currently in active deployment, with additional plant go-lives planned roughly every three months. The organization is adding analyst capacity because the implementation is generating more requirements, system changes, testing, and user enablement work than the current team can absorb.

This role sits between business analysis and systems analysis. Analysts follow requirements through technical specification, development clarification, functional and end-to-end testing, documentation, training, and deployment.

What You'll Do

- Work with business and domain leads to understand processes, clarify requirements, and identify how requested changes could affect the ERP and connected systems
- Document functional and non-functional requirements, business rules, process flows, data needs, use cases, and other artifacts needed to move work from business request to technical delivery
- Translate business requirements into technical specifications that development teams can act on, then remain involved to resolve questions and clarify intended behaviour during development
- Examine current processes and future-state requirements while distinguishing between needs that can be met through standard ERP functionality and requirements that need further configuration or development
- Build test scenarios and test cases, complete functional or end-to-end validation, and verify that delivered functionality reflects the documented requirement




- Prepare user guidance and training material, then work directly with end users as new processes and system functionality are introduced
- Develop deeper knowledge of one business domain while tracing dependencies across other processes, data, integrations, and systems

Basic Qualifications

- 3+ years of business analysis, systems analysis, or closely related experience that includes direct participation in an ERP implementation
- Experience gathering requirements from operational or business stakeholders and translating them into sufficiently precise specifications for technical or development teams
- Hands-on involvement in requirements documentation, system or functional testing, and validation of delivered functionality against business needs
- Experience working between technical and non-technical stakeholders when terminology, constraints, or priorities differ between the two groups
- Evidence of working constructively across functions, including revising requirements or proposed solutions when new business, technical, or system information changes the appropriate answer

Preferred Qualifications

- Experience with IFS, or substantial exposure to another enterprise ERP such as SAP or Oracle
- Domain experience in supply chain and logistics, manufacturing, sales and order management, or engineering processes
- ERP implementation experience in a manufacturing, multi-site, or otherwise highly integrated operating workplace




- Experience creating process maps, BRDs, system requirements, user stories, test cases, traceability documentation, or end-user training material
- Familiarity with Agile, Waterfall, or hybrid delivery practices and tools used for requirements, workflow, or project documentation

The Challenges

- The implementation is already in motion. Several plants are operating within the rollout while additional plants are being prepared, so analysis has to account for existing configurations, integrations, operational dependencies, and upcoming deployment work rather than starting from a blank system
- The program is intended to use standard IFS functionality where practical while still supporting business requirements that require customization. Determining and documenting the difference requires understanding both the process being requested and its downstream system effects
- Development capacity is available, but the upstream analysis, requirements, testing, and training workload has become a constraint. Analysts need to convert business needs into work that technical teams can act on without creating unnecessary rework or ambiguity

Your Impact

- Development teams receive clearer, better-tested requirements, reducing avoidable clarification cycles and allowing ERP work to move forward with fewer unresolved assumptions
- Business domains have dedicated analyst capacity to connect their operating requirements with the ERP and surrounding systems rather than treating each requested change in isolation
- Plant deployments reach users with requirements traced through implementation, testing, documentation, and training, strengthening the organization's ability to sustain its planned ERP rollout across the remaining sites

📌 Business Systems Analyst (Winnipeg)
🏢 Hammehr Talent Consultants
📍 Winnipeg