In this task you and other team members will review the following common implementation questions.
Common Questions
How long does it take to implement the system?
Compared to ERP systems, implementation is significantly easier because you continue to use your existing accounting system without any disruption to established processes such as payroll and banking. Furthermore, DBA’s accounting system uses a standard chart of accounts that is already set up for WIP accounting and absorption costing. Therefore, accounting setup is minimal.
Implementation time for the manufacturing system depends on three factors:
•The degree to which you are already organized
•The number and complexity of the items you make.
•The time and effort you apply to the implementation project.
If you are already organized in the sense that you have well established part numbers, BOM structures, work centers, routing processes, and locations, whether stored in your accounting software or in spreadsheets or documents, implementation can be accomplished relatively quickly.
On the other hand, if you will be establishing these master tables from scratch, especially work centers and routings, implementation may require considerably more time.
How much time is required also depends on the number and complexity of the items you make. If you have relatively few manufactured items with simple routing processes, implementation can be done quickly. On the other hand, if you have a high number of items with complex routings, implementation will take proportionally more time.
The final factor is the time and effort you apply to the implementation project. If you give the project high priority and enable team members to allocate generous time to the project, implementation can be accomplished relatively quickly.
System implementations range from a few weeks to several months. Follow the “building block” approach in the Startup Wizard, apply appropriate time and effort, and you can get up and running in relatively short order.
Do I need to cut over at the start of my fiscal year or any particular date?
System startup day can occur on any calendar day during the year. It is not tied to the start of your fiscal year or any accounting period start date. Therefore there are no artificial time constraints to compel anyone to cut corners or take half measures to meet a deadline. It is wise to set a target date to motivate your team, but make it a flexible date that gets pushed back whenever any tasks are not yet fully completed.
Can I continue using sales orders, inventory, and purchasing in my accounting system?
It is not possible to continue using these functions in your financial accounting system.
The manufacturing system must include all inventory-related supply and demand transactions so that MRP can generate the job and PO master schedule and set job and shipping priorities. Therefore, sales orders, inventory, and purchasing are required in DBA and must be inactivated in your financial accounting system.
DBA is not designed for partial use where you can pick and choose some functions and ignore others. If you are not committed to using the entire system workflow, you should not proceed with implementation.
Can I run in parallel with my existing system to help ease the transition?
Running in parallel is technically not possible because it would create double-postings and numerous data synchronization issues. Even if it were possible, instead of easing the transition, running in parallel would double the workload on users and is a sure recipe for failure.
The only way to make an easy transition is to use the step-by-step “building block” approach. This is done by completing all the tasks in the Startup Wizard in full so that the system is properly set up and all users are rehearsed and prepared for system startup day.
Can I use a consultant instead of doing it myself?
You are welcome to use a consultant to assist with implementation. If you do so, it is essential that you require the consultant to work within the Startup Wizard task structure and conform to its sequential order and startup day activation.
If your consultant proposes an alternate method such as incremental implementation or running in parallel, absolutely avoid doing so and consider ending the engagement because such methods have no chance of success. We can state this with authority based on decades of experience with hundreds of companies worldwide.
Be sure that you and your team are given access to the Startup Wizard so that implementation is an open and collaborative effort.
Can DBA run multiple companies?
Multiple companies, whether they are separate legal entities or operating divisions, are handled by your financial accounting system and its general ledger structure. DBA’s role is to manage each individual production facility and to update the central financial accounting system to reflect its activities. If you have multiple production facilities, each must be furnished with its own DBA system and product license (see next question).
Can DBA run multiple production facilities?
Yes, DBA can run multiple production facilities, provided that each facility is furnished with its own DBA system and product license.
DBA is designed to manage a single production facility with its own supply and demand transactions and where all inventory is local with no provision for transit time. Running each facility with its own DBA system provides total control and is much easier to use than a multi-facility ERP system.
Each DBA system uses the financial transfer to update the central financial accounting system to provide consolidated financial reporting at the enterprise level.
