The various tools we use to analyze business requirements, configure and implement, include the use of graphical flow diagrams to communicate the user requirements, as well as a project plan to monitor the progress of the project. These are agreed upon up front with the user and closely monitored throughout the project’s progress.

        Input

  • Orders
  • Journals
  • 3rd Party Integrations
  • etc

        Workflow

  • Access rules
  • Approvals
  • Document Routing
  • etc

        Process

  • Program Procedures
  • Data File Structures
  • Posting Rules
  • etc

        Output

  • Invoicing
  • Financial & Management Reports
  • Dashboards
  • Scheduling, Alerts & Notifications
  • etc

Input: How is Data Captured

In analyzing your requirements for capturing data into your system we consider the following:

  • Source documents
  • Number of users
  • Number of locations
  • Integration from other systems

Workflow: How is Data Routed

The approval and routing process you employ in your business will help to improve the security of your data and the efficiency in managing data in your organisation:

  • Only users sufficient rights can perform certain functions
  • Documents should go through an approval process before performing certain actions
  • Users can be alerted to pending approvals

Processing: Speed and Data Integrity are Key

The architecture of your network and the way the software is distributed will influence data processing. The following should be considered:

  • Hardware and networking requirements
  • Number of users
  • Number of locations

Output: Begin With the End in Mind

If you understand what needs to come out of the system (output), it will be so much easier to know what should go into the system, and how the data should be processed and stored so that it can be retrieved in a meaningful way. “Begin with the End in mind”, Steven Covey. Start with a dashboard snapshot of data relevant to your function in the organization, and then generate more detailed reports. Reports should be timely, accurate and useful for decision-making. Have critical data points and exceptions communicated to you through setting up an alert or notification in the system.

Project Plan

Once the requirements are established from the current and proposed new system, we can determine the scope of the project and then translate that into a project plan. The plan is designed and agreed with the client. One of the primary goals of the project plan is to ensure that it fits the clients budget, and that it should serve as a guide for the implementation of the project. Part of our success in meeting our project plans and delivering on time, is that we take note of where you are in the life cycle of your business, and through experience, we work with the client to develop a plan that is commensurate with the business’s resources and capabilities.
Our software implementation methodology that we employ goes a long way to ensuring our success to implement an appropriate business management software solution.

Process Review

This is considered one of the most important parts of the project. We will do an initial investigation and understanding of your business in order to recommend an appropriate system and develop an initial project plan, but a more detailed process review of your current and proposed requirements takes place at the start of the project. Our experience, and a proven software implementation methodology, helps us to gain the right insights into your business. We are very well versed in the latest tools and technologies for customizing the software, but we always lead with the business, and make recommendations that are appropriate for your business.