Driver Scheduling and maping (almost like a deliver route program)

We are a parking enforcement company for private properties (we aren’t big at all) however we manage a big client that has about 900 properties across Ontario Canada. Our business is very unique but also very selective (or picky shall we say). We require a tool where we can meet these selective requests depending who’s available and who is registered per city. Think of this tool kind of like a delivery route program, where certain drivers need to go through a specific route, or certain drivers have a special license to drive a certain truck. And at the same time, think of this program kind of like a Pilot’s flight plan – we can only goto certain countries or cities at certain times or certain pilots can only enter certain cities than others, and some “pilots” can enter all of them. Here is what we need: Portfolio portion of the program We will create a portfolio for each property, under this portfolio there will variables we need to enter. Here are most of the variables: - Name of profile. - What City: (we need to be able to add more in the future) - How much time does this site take to enforce? o Enter minutes - How many Rotations a month: 10 rotations (for example) maybe 22 - Is this site 24/7 rotation: Yes or No o No – Define Times and Dates ( example: during certain hours of the day or night and which days) o No – Can’t be hit on weekends, or can’t be hit on a certain weekday/night o No – Does this site need to be hit at certain hours? (ex: between 9am to 5pm) o Yes – Proceed. - Is this property a chalking site(meaning some sites require us to return after a certain time): Yes or No o Yes – how much time is the chalking on site: (30 minutes for example) o Yes – The program needs to place the property on the run sheet again o No - Proceed - Should this property be attached to another profile? Yes or No? o No - Proceed o Yes – select a profile that will be hit together with another profile but not exceeding the number of rotations.  For example: • Profile A – 10 rotations • Profile B – 8 Rotations o Once profile B has completed the Rotations, then only add in Profile A to the run sheet. - Is this profile reoccurring every month (repeat same settings) Yes or No o Yes – Proceed o No – place a reminder at the end of the month of this portfolio to review - Wirtten comments (for example): o This property can tow, with x Company with X Division.  This information will show up when printing the run sheet. - Add buttons like, Done, Edit, Delete. That is the Portfolio portion of the program. Now we need to add Officers (Staff). - Employee Name: - Enter Schedule of employee (modified every 2 weeks) o Here we will select the start to end hours and what days they are to work. - What Cities can this employee operate in? o As we add more cities we need this also to be updated. o This will be a check box option I guess for simplicity. - How many profiles can this officer hit per session? (enter a number, probably 25) - Add buttons like, Done, Edit, Delete employee That is the employee portion of the program. Data Entry portion of the program This program needs to assign a serial code, or a number to each printed run sheet so everyday someone can enter the run sheet number and update which properties got hit, and which properties did not. Layout example: - Run sheet number 10011 o Shows all the profiles that were supposed to be hit in a list o Check box if it got hit or not: Yes Or No  Yes or No – records get updated - Show reaming hits (rotations) per portfolio o This can be a separate window, it’s more of a reporting window - Buttons: Done, Edit, Next, Delete Run Number This information will be entered on a day to day bases so the program knows how many visits are left. If the data does not get entered, the program can assume they have been hit until the run sheet is updated. Now we need the program to generate a Run Sheet and Print these run sheets on paper. PLEASE REVIEW ATTACHED DOCUMENT FOR THE REST OF THE DETAILS!