Contact
All services

ERP implementation and system integration

Connect the operation, ERP and equipment.

Purchasing, production and the warehouse need to work with the same items, quantities and status information. A recipe, a stock transfer or a packing step has to work in the system and at the workplace.

The scope covers Microsoft Dynamics 365 Business Central implementation and project management for ERP, warehouse software and equipment integration. Depending on the mandate, the work includes developing processes and master data, configuring the operational setup, managing suppliers and tests, and preparing migration, training and the transition into operation.

Specify what happens at each handover

Process definitions developed with operations, IT and suppliers allocate functions to the ERP, warehouse software, controls and people. Master data, stock ownership, order release, transport and confirmations need agreed rules. Existing software capability is checked before additional functions or systems are proposed.

The process description also covers a blocked destination, an unreadable label, an unsuitable load or a missing message. It sets out what the operator can do, how the process can restart and how the systems are reconciled afterwards. Design changes are checked against the agreed requirements and their effect on cost, schedule and tests.

Business Central from process design to operation

Process development with the operating team covers purchasing, inventory, production and sales. Items, units, bills of materials, replenishment, batches and costs need to describe how the business will work. The work includes preparing and reconciling master data, configuring the agreed operational processes and testing complete flows, including corrections and returns.

At Roam Electric, I implemented Business Central and managed the warehouse operation. My current food-production work connects recipes and intermediate products with packing, stock and sales in a configured test environment. User tests, partner reviews and the move into live operation are separate project steps.

What you receive

  • System responsibilities and interfaces

    Process and data descriptions across the ERP, WMS, material-flow controls, production systems and equipment, including manual steps and exceptions.

  • Test cases and acceptance criteria

    Expected results linked to requirements, with prerequisites, test data, responsibilities and evidence for the agreed factory, site, integration and user tests.

  • Defect follow-up and acceptance evidence

    Recorded results, unresolved defects and retests, with their effect on operation and the decisions required for acceptance.

  • Cutover, ramp-up and stabilisation

    Preparation for migration, temporary operations, training, staffing and fallback within the agreed role. During ramp-up, an issue list records operating impact, responsibility, planned corrections and retest results.

Test the intended operation

Test planning focuses on flows that will use the same capacity at the same time. Each test needs suitable stock, data, staff and connections to the systems involved. Before cutover, the team agrees the sequence, fallback arrangements and conditions for restarting. Test records show unresolved defects and their effect on operation so the authorised client representatives can make the contractual acceptance decision.

Illustrative interface test

The pallet arrived. Its confirmation did not.

A pallet reaches its destination, but its arrival confirmation is lost. A retry could duplicate a stock posting; an unresolved task could prevent the next order from proceeding.

  1. 01

    Set up the interruption

    In an agreed test environment, interrupt the confirmation after the physical movement and record the state in each system.

  2. 02

    Check recovery

    Restore communication and verify the agreed retry behaviour. The recovery must avoid a duplicate movement or stock posting.

  3. 03

    Check the operator's view

    Check that the physical stock and system records match, any remaining fault is visible to the operator and the agreed recovery procedure can be followed.

The actual test sequence depends on the agreed system architecture and recovery procedures.

Related project work

Planning example: comparing two warehouse concepts

Practical questions

What do you implement directly?

For Business Central, my work includes process design, master data, operational configuration and testing. I can lead the implementation with your operating team and software partner. Programming, extensions and other supplier deliverables are assigned in the project scope.

Can you help with an approaching or difficult go-live?

Yes. A review identifies the processes, interfaces or defects preventing the intended operation. I agree priorities, responsible parties and tests with the delivery team. Support can continue into ramp-up under a defined mandate.

When should acceptance criteria be written?

During specification and procurement wherever possible. Performance conditions and responsibilities agreed before contracting give later tests a defined basis. If they are missing, they need agreement with the relevant parties.