We have managed to collect and define the most popular questions of our visitors and clients. Here you'll find the best articles and recommendations concerning the questions on selection, implementation and management of your products.

  • The product engineering team has put together a product framework around ERP, CRM, Financial Accounting, Warehousing, Healthcare, HR & Payroll and Projects.

    All features and industry specific enhancements on these products are stored as business components that are integrated, tested and stored as objects in a business repository. This offering is customized to meet the specific requirements of customers. The products offers good controls combined with the required flexibility.

    In simple terms, the product offering is a set of features and functionalities readily available. Pick and choose what you require and quickly get started…

  • Systems are designed to provide data based on the inputs that they receive. A well-tested system will generally not give incorrect data. We provide a good after sales support process that ensures that such problems gets addressed.

    • Light Business Applications
    • Powerful Analytics
    • 4th Level of Normalization
    • High Portability & Security
    • Easy Config & Deployment
    • User Friendly
    • Multi Lingual Support
    • Pure Web Applications
    • Mobile Ready Applications
  • An implementation of a solution for an organization involves customizing the product to meet the business needs of a client within a definite time frame.

  • There is a need to invest on documentation of the solution over a period of time. This involves establishing a training manual, which includes guidelines and documentation. The company using such solutions must provide orientation programs for new users.

  • During the requirement-gathering phase of the implementation, business requirements are captured. This requirement will be built in the solution and deployed. If the company wishes to change this requirement, a change request process is initiated post stabilization of the implementation.

  • Changes in requirements are not addressed beyond an agreed timeframe during the implementation as this impacts the timelines of the project.

    The customer can decide to change the business requirements after doing a thorough evaluation of the impact on the project in terms of project costs, timelines, additional efforts and the perceived messaging this has in the minds of business users.

  • Systems are designed to provide data based on the inputs that they receive. A well-tested system will generally not give incorrect data. We provide a good after sales support process that ensures that such problems gets addressed.

  • It is important for the company to create a backup of the transaction data on a regular basis. We will be able to provide for a fresh instance of the application which can then be used with the data backup.

  • The data for the first time is loaded using excel uploads based on the volume. For regular entry of data, entry screens are provided. Necessary training for the users to make use of the data entry screen would be useful for a successful implementation

  • “What you feed is what you get”. Accuracy of the data depends on the data entry and the business logic provided. Data validation screens can be provided on request during the course of the implementation.

  • One has to establish the facts on why the timelines agreed are not met. If the reasons for delay are clearly emerging from the implementation company, the implementation company pays for the same. If the delays in the project arise from the client team, the client pays for the same. If we are able to follow a good project plan coupled with the right escalation matrix, agreed timelines will be met.

    • Time spent by the users
    • Rotation/change of users
    • Change in requirements leading to rework
    • Clashes during implementation between stakeholders of the project
    • Freedom to work is required across layers of the organization
    • Data entry or using the system requires a lot of follow up
    • User expectations include multiple reports, which can be time consuming
    • Existing records and data is not correct and accurate
    • Expectation to put old data into the system not appreciated by users

    User adoption of the system is the key to success. Some key implementation tips include.

    • Users should not feel like “we must not use this system”
    • Tackle people in a friendly manner to use the system
    • Train the users from system basics
    • Do not make users sit after office hours
    • User changes should be addressed quickly
    • Reports or changes required by users not relevant for management to be carefully addressed

    The additional manpower requirement for users during implementation should be addressed. Complete change is system requirements will lead to implementation failures. This should be explained correctly to users to gain their buy in.

    Challenges of providing additional features within existing processes and roll back to previous process should be explained and managed effectively to users for a successful implementation.