IT Business Analyst — Purchasing

Miracle Software Systems, Inc., are actively looking for IT Business Partner — Purchasing to work W2 position for one of our direct client at Remote.

Requirement Details:

IT Business Analyst — Purchasing
Long term
Remote

Position Summary: 
The Purchasing IT Business Partner is the dedicated partner to procurement. Purchasing runs through the plant ERP today, with the future-state direction set through the broader ERP path, and purchasing analytics and automation are active areas of investment. This partner owns procurement requirements across plants and corporate — and documents how purchasing actually works site to site as input to standardization. 
    
Key Responsibilities:

• Serve as the single point of contact between Purchasing and IT — the front door for demand from the area into IT delivery, and the standing voice of the area inside IT. 
• Bring the art of the possible to requirements conversations — working knowledge of the area’s core systems, so the business sees what existing platforms can already do before new build is assumed. 
• Elicit business requirements through workshops, interviews, and direct process observation, and capture them in the requirements toolset (Azure DevOps) with traceability from need to build to test. 
• Map current-state business processes and define future-state processes with the business ahead of any build, so programs start from agreed scope rather than assumptions.
• Manage requirements through their life cycle — prioritization, change control, and formal business sign-off before build begins. 
• Write requirements and acceptance criteria that are clear, testable, and buildable, and plan and support user acceptance testing with named business testers and recorded sign-off.
• Own business readiness for what ships — training coordination, adoption support, and post-go-live evaluation of whether the solution delivers the value intended. 
• Help the area’s leadership shape and prioritize demand — keep a rolling view of what IT has in flight for the area, what comes next, and what it will take. 
• Own requirements for procurement processes across plants and corporate — purchasing, receiving, supplier management, and approvals. 
• Document process variation between plants as input to standardization, and carry supplier data and integration requirements. 
• Support purchasing analytics and automation requirements — spend visibility, approval workflow, and reporting. 
• Support procurement-relevant requirements in the ERP direction as the platform path is set. 

Required Qualifications:

• Bachelor’s degree in Business, Information Technology, or a related field. 
• Minimum 5 years of business analysis experience on enterprise system implementations or major process-change programs. 
• Demonstrated elicitation and documentation skill — requirements workshops, interviews, and process observation with business users at every level. 
• Experience with process mapping and current-state to future-state definition. 
• Experience managing requirements in a tracked toolset (Azure DevOps, Jira, or equivalent) with traceability and sign-off. 
• Experience planning and supporting user acceptance testing with business testers. 
• Working knowledge, at a super-user level or better, of at least one core system in this area (or a direct equivalent) — enough to speak to what the system can do when shaping requirements with the business. 
• Experience supporting procurement or supply chain processes — purchasing, receiving, or supplier management.  

Preferred Qualifications: 

• IIBA certification — CCBA or CBAP — or PMI Professional in Business Analysis (PMI-PBA). 
• BRM Institute training or certification (BRMP) for the business-partner dimension of the role. 
• Hands-on experience with ERP procurement modules — Oracle Fusion, Microsoft Dynamics NAV, or equivalent. 
• Experience in a multi-site manufacturing, distribution, or retail company. 

Skills and Competencies: 

• Elicitation and facilitation — draws out what the business actually needs, not just what it asks for. 
• Written clarity — writes requirements a developer can build from and a tester can test against. 
• Process thinking — sees the workflow behind the request and the exceptions behind the workflow. 
• Stakeholder trust — becomes the person the business area calls first. 
• Prioritization judgment — helps the business sequence what matters against what is possible. 
• Ownership through adoption — stays with the work through testing, training, and go-live, not just documentation.       

Success Metrics: 

• Requirements for Purchasing are clear, documented, and agreed before build starts. 
• The business area treats this partner as its first call into IT. 
• User acceptance testing runs with named business testers and recorded sign-off on every release that touches the area. 
• Fewer late-stage surprises and fewer post-go-live changes traced to missed requirements. 
• Adoption is measured and owned — the area uses what ships.