|
|
| NetSuite Implementation>
|
| |
At Elevation9. we follow a tried and trusted NetSuite implementation methodology. Configuring and implementing NetSuite takes on the following steps:
> Gap Analysis. Similar to a fit analysis, the purpose of this document is to plan the project and all the steps that need completing based on business requirements. Key gaps between the business being implemented on NetSuite and the product are identified during this stage to ensure that we have resolutions that are clearly mapped out.
> Macro Setup. This is the process of enabling and disabling features of the product based on business requirements. During this stage, the all important Chart of Accounts are defined and the item structures. Both of these definitions need to be professionally produced to avoid unexpected results.
> Micro Setup. This is where the application is configured at the micro-level. Items such as sales tax rules, shipping and handing, marketing strategy, salesforce automation rules, revenue recognition schedules etc etc are setup ensuring your success in meeting business requirements.
> Prototyping. This is one of the most important steps during implementation. NetSuite is typically a non-technical implementation but does require extensive product and business knowledge to do it right. Prototyping is where every real-world situtation from lead to cash and return authorizations to refunds are emulated using real data. The system is then fine-tuned to ensure optimal useability and efficiency for your business. During this process the customer is engaged with the project team to ensure knowledge transfer occurs in preparation for the go live date.
> Data conversion. This is an important step in the project and setting expectations here are paramount. It can make the difference between a successful project and one that never gets completed. Data conversion is the process of identifying data to be moved from the legacy systems into the new NetSuite system. It is one of the later steps during an implementation since its important that the account is configured first to ensure correct mapping.
> Customization/Integration. This is a step that should take place after implementation in a phase II of the project. However, sometimes it is necesary to implement certain scripting customization and integration initiatives to meet important business requirements. Customization includes scripting, dashboard setup, reporting, adding fields/records, producing saved searches, business process automation and much more.
> Handover. This is a high-level user document that is tailored to your business to explain important aspects of your new system. It is also where the project is accepted.
> Cut-over. This is the process of sending your system live and into full production. It includes pre-requisite steps like setting up beginning balances for accounting and inventory and final data conversions
> Post-implementation. This is a optional and includes post implementation support, mentoring and training activities. Business tend to be a very dynamic thing and changes happen all the time to your original business model. It is important that these changes are reflecting in your system in a timely manner. |
|
|
|
|
|
