ERP systems such as Microsoft Dynamics NAV support the standard processes of an organisation. They integrate best practices that have provided an effective and validated way to perform business operations. To select and successfully implement an ERP system, the capabilities of that system have to be compared with a company’s business needs. Based on a comparison, all of the fits and gaps must be identified and further analysed. This step usually forms part of ERP implementation methodologies and is called fit gap analysis.

Fit gap analysis (also called gap analysis) is an important phase of an ERP selection and implementation. It determines the extent of business process change required for a particular solution as well as software customisation and interfacing requirements. Matching the ERP’s functionality to the way an organisation does business is a vital factor for the success of an ERP implementation.

Fit gap analysis is mentioned twice in ERP system implementation methodologies. High-level fit gap analysis is usually conducted in the pre-implementation or ERP system selection phase and a complete or detailed fit gap analysis is completed during system analysis phase. Fit gap analysis is usually built on a Functional Requirements Document (FRD). FRD provides a detailed list of the functional, non-functional, integration and interface requirements and the affected business process flows.

Matching the ERP’s functionality to the way an organisation does business is a vital factor for the success of an ERP implementation.

The main goal of fit gap analysis is to identify and document all fits and gaps, followed by an analysis of each gap, suggestions of possible solutions and closing of the gaps by selecting the most appropriate option. Possible options are:

  1. Standard ERP system capability: Standard capabilities are met by the system out-of-the-box, without requiring additional effort or configuration time.
  2. ERP system configuration: This entails choosing from among the reference processes and setting the parameters in ERP to reflect organisational features without changing the ERP source code.
  3. Adapting a company’s business processes: Best practices implemented in the software package are applied within an organisation (technology-driven approach).
  4. Adapting an ERP system through customisation: Adaptation of an ERP system is appropriate for those companies that believe their business processes are better than those implemented in an ERP system and do not want to lose their competitive advantage.
  5. Adding a new business solution and/or software vendor: A third-party vendor (independent software vendor, ISV) can provide a vertical or industry solution that supports a customer’s specific needs. For example, the enwis) waste managment solution.
  6. Providing a workaround so that the business can function: Business needs will not be supported and will be documented as out of scope or planned for future releases.

Fit gap analysis holds important consequences for project success. One of the output metrics of the fit gap analysis is the degree of fit. The degree of fit is an indicator of business alignment with the standard ERP system functionality. It is calculated as the sum of all business needs that fit, divided by all business needs. Besides standard ERP system capabilities, the business needs categorised as fit are ERP system configurations and adaptations of a company’s business processes. In addition, each business need should be weighted in terms of its importance (e.g. nice-to-have or critical).

Even though the metric is only an estimate, it provides a high-level overview and understanding of the project risk. A low degree of fit could also lead to a decision to select another ERP system or to redesign business processes to meet the standard system.

mm
Written By Dejan Pajk

Dejan joined Fenwick Software in October 2015 from Slovenia where he had gained eight years’ experience in NAV development and consulting. After completing a master's degree in 2009, he was appointed to a junior researcher position at the University of Ljubljana’s Faculty of Economics. His research interests included reference models and business process modelling. He has taught graduate and undergraduate courses and also implemented the Microsoft Dynamics Academic Alliance (DynAA) university program. Dejan is a Microsoft Certified Trainer (MCT) for Dynamics NAV and certified member of Australian Computer Society.

Leave a Reply

Your email address will not be published. Required fields are marked *

We're here to help!

Call us

03 9695 3333

Or, leave us a message