DBA Manufacturing is a completely different product
DBA Manufacturing is a completely different product than DBA Classic.
Different Origin
DBA Manufacturing originated from a software package named Ezijobz SME, which we acquired from another company in 2003. It was re-branded with the DBA name in late 2004 when our programming team took over product development.
Different Technology
DBA Manufacturing's technology is completely different than DBA Classic’s technology. It is written in a different programming language (Delphi vs. TAS) and uses a different database (Firebird SQL vs. Pervasive).
Different Multi-User Control
Both systems limit the number of users who can access the system at any given time to your licensed user count. DBA Manufacturing has an additional restriction whereby the number of user logon ID’s that can be designated as “active” is limited to your licensed user count.
NOTE: In some cases this may require purchase of additional users when converting to the new system.
Different Feature Set
The two products serve the same target market – manufacturing businesses – and have many of the same modules, but the similarities end there. Within the modules the features and functions are quite different.
Different Support Model
Unlike the old fee-for-service support model used with Classic, support for DBA Manufacturing is Internet-based and is provided via a flat fee support subscription.
The decision to convert is yours alone
We are neutral in regards to which system you use. Only you can make the decision to change systems. You must look at DBA Manufacturing objectively like you would any other new product and decide if it’s in your best interest to make the change.
Follow the Startup Wizard
If you decide to convert to DBA Manufacturing, you must go through the exact same implementation process that any other company would undergo coming from a non-DBA system. This means that you must complete all the tasks in the Startup Wizard.
The Startup Wizard provides videos and documentation that guide you through a set of sequential setup and rehearsal tasks leading up to system startup day. If you have a question within a given task, you can submit a support ticket and we will help you. By the time you get to startup day, your system will be properly set up and users fully rehearsed for live operations.
Use the standard chart of accounts
DBA Manufacturing is supplied with a standard chart of accounts that is optimized for manufacturing and for the DBA Manufacturing system. Instead of using your existing chart of accounts, we provide a means whereby you cross-reference your old accounts with the standard accounts and add new accounts for any exceptions.
Multi-Currency is not supported within the DBA Legacy Financials
If you are using the Legacy Financials accounting configuration, be aware that the legacy financial modules --Accounts Receivable, Accounts Payable, and Banking – have no multi-currency capabilities. For multi-currency processing you must convert to the Financial Transfer accounting configuration and a mainstream accounting package for financial processes (receivables, payables, banking, payroll, overall general ledger).
Financial Transfer Guide Multi-Currency
Using a Mainstream Accounting Package
Do not convert without a support subscription
Any company that converts to an all-new manufacturing system cannot realistically do so without any training and support.
Our flat-fee support subscription is resource-based and provides value to all your users, whether your company uses support tickets heavily or not at all. During the conversion process you will most assuredly have questions and will benefit from our help.
Support: What to expect and not to expect
The Internet-based support model we use with DBA Manufacturing is quite different than the fee-for service model we offered in the DBA Classic era. It is more affordable, more responsive, and offers many more self-help resources. Here are some things to keep in mind as you get involved with our support program.
Expect support to be an ongoing cost over the life of the system
You should not attempt to convert to DBA Manufacturing on your own and should budget for a support subscription. In fact, we advise customers to maintain a support subscription over the life of the product. To encourage this, after your initial 6-month subscription expires, you receive a special renewal rate that is discounted by $200 that stays in effect for as long as you continue your subscription without interruption.
Do not expect “per incident” or free support
The purpose of our support subscription model is to eliminate fee-for-service billing in favor of a low-cost flat fee that is affordable for all. Therefore, we do not offer any type of “per incident” alternative. We also do not provide any free or “back channel” support for system installation or updates.
Do not expect to pick up the phone
Without exception, all support is initiated through a support ticket. The ticket queue is monitored throughout business hours and channels all support requests through a central system. We do not have a support phone number. Please do not call our sales office for support-related issues.
Do not expect our support staff to be familiar with DBA Classic
Our support staff knows DBA Manufacturing well, but not one person on the staff comes from the DBA Classic era. So when you submit tickets, please don’t compare and contrast how DBA Classic did something with the way DBA Manufacturing does it because it will have no meaning to our support people.
Data Transfer: What not to expect
Do not expect complete data transfer
The DBATRAN utility only exports master tables. It does not export open sales orders, work orders, purchase orders, customer invoices, supplier invoices, or transactional history. For some time after the conversion you will want to retain access to Classic in order to reference historical information.
Do not expect guaranteed data export
We cannot guarantee that the DBATRAN utility will work for all Classic systems. DBATRAN only works with certain version of Pervasive and may not work on systems that have been altered with custom programming or add-on products such as Evo-ERP. DBATRAN does not work on some systems for unknown reasons.
So try DBATRAN and hopefully it will work for your system. If you cannot make it work, you can export data on your own using the Pervasive Control Center.
Hardware & Network Considerations
A final factor to consider before making a conversion to DBA Manufacturing is the status of your hardware and network. DBA Classic uses older technology that runs on older machines. DBA Manufacturing. like most newer software programs, requires more memory, more processing power, and a faster network. You should review our system requirements, which are listed in our Installation Guide, and upgrade your equipment and network if required.
