Need of a Windows based calendar and interface allowing users to choose settings for an access control system. On average they would need to choose a lock & unlock time for each day. The user should be able to select all weekdays or particular days of every week when making settings. For example if the user wants to trigger the system every weekday at 8AM & 5:30 PM except on Tuesdays when the second trigger is 7PM this should only take a couple of steps like a reoccurring event in Outlook. They should be able to select every Mon, Wed, Thur and Fri for one setting & every Tues for the other. They should be able to go in & change any one day's, or multiple day's setting without effecting other occurrences. The user should also be able to select individual holidays from a list such as all US or Canadian holidays or be able to manually select holidays. Would also like the user to be able to create, select & view "categories" like in Outlook. This would allow the user to have a category for individual locks if they maintain more than one like a property manager. A category might be "Building 1, front door".
Calendar will need to export to an external memory such as a compact flash or SD card as a .txt in FAT12 or FAT16 format with the following ASCII data format: MM/DD/YYYYLHH:MN
MM = month
DD = day
YYYY = year
L or U - L = Lock/Unlock
HH = hour in military time
MN = minutes
Example 1: 01/14/2007U01:25; Unlock the door at 1:25 AM on 1/14/2007. (16 ASCII Characters)
Example 2: 11/02/2007L22:00; Lock the door at 10:00PM on 11/2/2007. (16 ASCII Characters)
I have also attached several screen shots from MS Outlook showing what we would like the interface to look like as well as it's capabilities. We are basing a lot of what we are looking for around Outlooks because it is so commonly used & a proven standard.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
Windows 98, Windows 2000 & Windows XP