Show/Hide Toolbars

DBA Help

Navigation: Startup Guide > Phase 2 - Orientation

Startup - Implementation Rules

Scroll Prev Top Next More

In this task you and other team members will review the following implementation rules.  

Implementation Rules

Here are six basic rules that must be followed for self-implementation to work properly and provide good results.

1. Use the Startup Wizard  

You must use the Startup Wizard for active guidance throughout the implementation project.  Click each task name to link to a corresponding topic in the Startup Guide that explains how to perform the task.  As each task is finished, it is checked as completed, which opens the next task.  

NOTE: If you choose to work with a consultant, make sure he or she uses the Startup Wizard and adheres to the rules and guidelines expressed in this guide.

2. Designate a project manager

One person must be designated as the implementation project manager to assign tasks, flag tasks as completed, and provide overall leadership.  

3. Complete tasks in the order listed

It is essential that tasks are completed in the order they are listed within the Startup Wizard.  This provides the “building block” effect and insures that supporting tables get populated prior to related master tables.

4. Do not skip tasks

Do not skip any tasks listed in the Startup Wizard.  This insures that all elements of the “Total Control” workflow are set up and ready for deployment on system startup day.

5. Finish each task to full completion

Never partially complete a task because it will adversely affect workflow processes when the system is activated.  Finish each task to full completion before moving on to the next task.  

6. Do not cut corners with the three "super tasks"

It is vitally important that the three "super tasks" listed below are fully completed because they provide the foundation for product costing, inventory control, MRP, and shop control.  

Routings

Locations

Item MRP Settings

7. Activate the entire system on a single startup day

Due to the integrated nature of the “Total Control” workflow, you must activate the entire system on a single startup day so that all core elements of the system are deployed on day one.