WF Voice and Data,
I am not sure how long you have been installing the MiVO-250, but at some point it would be a wise idea to get all of the technicians together and create a default database that works for the majority of installations so you don't have to deal with making the same changes every time your start programming. This will also help your service group as things will be more uniform going forward.
As for how to program I think everyone does that in whatever order makes sense to them, but here is how I handle it at a high level.
1. Program all Resource Cards: T1/E1/PRI, LSM-4, SLM-4, DDM-16, etc..
2. Program all Devices: Phones, Phantoms, Hot Desk Users
3. Program all Groups: Extension Lists, Hunt Groups
4. Program all Call Routing Announcements
5. Program all Extension Lists and Mailboxes
6. Start Call Flow Programming
7. License System
8. Label Chassis
In reality though I already have a default database that has 1 Phone, 1 Hot Desk User, 1 Phantom, 1 Mailbox already setup using our standards that I use to Copy/Paste from. I also have created default Keymaps as well so that makes it easier to get phones out and make changes as required later. It also has our standard Day and Night Auto Attendants and Directory Call Routing Announcements as well as Message Notification, Record-A-Call and Voice Mail applications.
I Import information in using the User's Import form as that can create Phones, Phantoms, and Hot Desk Users all at the same time. The drawback is that is will also create mailboxes for them; which I delete if they are not needed and then create Extension IDs. Keep in mind that you can add fields to the Import list such as Password so it will also put in the password for user web access.
Also, you can create yourself some SIP Trunk Group files [stg] after you figured out how to make it work that will speed up programming on those as well; here you can also make changes and add fields as long as you know what to add to get the results you want; I have not found a way yet to program Route Sets though.
Thanks,
TE