Single Person Needs The system must be able to schedule a block of time and allow entry of details for that time slot. o time slots can be as little as 15 minutes and don't have an upper boundary on length The system must be able to define recurring blocks of time (daily, weekly, monthly, etc). The system must be able to view the calendar in a per day, work week, 7 day week, or month basis. o should have the ability to run a report and just list the activities in a certain date range. The system must have ability to create calendar items that aren't scheduled for a specific time during the day but mainly serve as a reminder associated with a specific day (or set of days). The system must allow for an individual's calendar items to be entered and viewed offline. Multi-Person Needs The sytem must have calendars definable for every person in the company. o should be able to define calendars for abstract "things" (e.g., conference room, projector, release train, etc.). The system must allow one person to view other calendars. The system should be able to view multiple calendars overlaid atop each other (eg, viewing a composite schedule for a group of people looking for overlaps in vacation times). o should be able to save off which calendars defined the grouping being viewed so that the same grouping can be queried later for a different (or the same) time range The system must be allowed to define time blocks that hide details of the item so that others can't see it. The system must have the ability to invite others to partipate in an activity at a specific time. o should show that others have conflict with a proposed time slot before entering the proposal o could do a search and find the first available time slot open for all invitees o should have ability for invitee to respond and have sender be notified of response Project-Centric Needs The system must allow for someone (sys admin?) to enter in activities that appear on everyone's calendar (i.e., holidays, company meetings, etc.) These items probably appear as notes for a specific day(s) versus as an actual block of time. The system should have the inherent ability to define which projects are being worked on by a person on a given date. These project assignments should be entered by either the individual or perhaps that person's functional manager. The idea is to be able to determine individual's focus for a given length of time as planning is being done. This type of capability could be simulated by a generic mechanism to define blocks of time, but this "project information" probably has different characteristics that a normal time block (e.g., a day slated to work on Project X wouldn't show that person booked the entire day such that other meeting proposals would show conflicts; however other project assignments would show conflicts). The capability also would need the ability for a person to be assigned to work on multiple projects on a given day (ie, the level of granularity probably needs to be in hours). Environment/Platforms The system must be used by everyone in the company. Since it may be impracticle to get everyone to migrate off their favorite calendaring system, the tool must be easily synchronized (i.e., on a daily on semi-daily basis) with the following commonly used calendaring tools: o MS Outlook o Others? The tool must be available on Windows NT.