Case Study Information

  • Project Name: Terbium - Procurement, Inventory, Warehousing & Distribution Solution
  • Industry: Chemical Sector
  • Complete: Date July 2014
  • Type: ERP Solution
  • Resources:

    In-house project team. Project implementations using PRINCE2 & Agile Methodoligies.

Statement of Requirement

The business requirement was based on the integration of several processes which were segregated and based on different software solutions. Principal sectors included Inventory Management, Maintenance of Assets, HR, Financial Cost Management, and a Suite of Reporting Tools. Within each sector was a number of sub-sections, by applying logical integration links into development modules this allowed a stepped program of development. The business select teams for each stepped program which facilitated weekly updates and monthly reviews resulting in a smooth delivery of the application installation.


The software design being modular based is linked to the business workflow. By working with the four sub-modules allowed a systematic set of protocols to be applied by both the in-house team and the external development team. As each sub-module was design and developed it was added to a live test server allowing the in-house team to test all aspects of the sub-modules and their integration into the primary module.
Module Development Structures

  • Module A 1 of 3
  • Procurement.
  • Legal Contracts.
  • Purchasing.
  • Goods Received.
  • Module B 2 of 3
  • Warehouse Management
  • Maintenance Management
  • Deployment
  • Workshop
  • Module C 3 of 3
  • Human Resource
  • Tracking & Reporting
  • Application Support
  • Business's App Admin

Within the development was a requirement for data population the process was implemented on completion and sign off the sub-module.

Testing and Development

Development of the solution was applied using PRINCE2 project management methodology to plan each stage of the project this ensured that the project was delivered on time and within the budget. The key deliverables made use of JIRA an Agile framework inclusive with Scrum & Kanban, two of the most prominent methodologies under the agile umbrella. Scrum, focused on planning work in short sprints, while Kanban was geared towards the continuous release of sub-modules that could be tested.

Testing is carried out on a test server. This approach was adopted as the project required a complete replacement of all business modules. Each of the sub-modules were tested by the in-house IT team and selected users of the module, this allowed for rapid adjustments in the workflow should it be needed. Once all sub-modules were completed the main Module was installed. Integration into the associated software processes of the original software applications was achieved using Application Programming Interfaces (API’s) routines for data transfer.