Campus Calendaring Requirements

Server Requirements

• Interoperability with planned campus directory services.
  • LDAP Authentication
• Store the data on the server
  • Server tracks the location of a user accounts calendaring data, client does not need to know where it is stored.
  • The end user does not need to know which server is housing the calendaring data, if it is stored across multiple servers.
• We need to specify the number of accounts needed to accommodate, and ensure any solution scales to that number.
• Server is capable of integration with other server types (iCal, CalDAV)
• We need to determine how much storage will be needed.
• Simultaneous connections are needed.
  • How many are supported by any given solution?
  • Is it a hardware limit or a software limit?

Client Requirements

• Web Interface for viewing from an outside location with a currently supported browser.
• Web Interface is section 508 compliant for accessibility
• Client is available for vendor supported operating systems (MS, Apple)
• Interface with Outlook
  • Can Outlook connect to both an exchange server and another calendaring server simultaniously?
• Link to a local mail client
• Cross platform client support
• Syncronicity to smart phones, PDAs and mobile devices
  • Multiple formats of PDAs, Palm, Mobile Windows, etc..
  • The more they support the better we consider them.

Security Requirements

• Public and Private calendaring
• Privacy exclusion per calendar entry
• Multiple level access control
  • Need to be able to have an assistant schedule events for a supervisor
• De-centralized administration

Reliability Requirements

• Redundancy
• Scalability
• Minimal downtime (critical system)
• Real time
• Backups preformed without disruption of service
  • Ideally backups should have an understanding of the calendaring data, such that a single account's calendars could be recovered for a given section of time.
  • Provides for retention periods that correspond with the UO/OUS records retention schedules

Licensing and Support Requirements

• Simple, scalable licensing scheme
  • No named user license.
  • No per user license scheme
  • Must be able to be summarized in 3 sentences or less (Good Luck!)
• Sane support contract for customizing or configuring the software

Cost Requirements

• ?

Functional Requirements

• Scriptable account administration.
• Comparison of free/busy times across calendars
• Recurring Appointments
• Time-configurable Appointment reminders
  • Audible and Email ticklers
• Ability to migrate calendars from one account to another.
• Ability to export / import calendars, within reason.
• Group calendars
• Task and to-do list management
• Able to include links to related files, URLs
• Address book importability
• Delegated control (ie. assistants entering a bosses calendar information, etc.)
• Extended Calendar events (events that span multiple days)
• Holiday Support
• Scriptability desired.

Technical Requirements

• I would think that in an attempt to support interoperable client implementations, that RFC 2445 support would be a requirement. "Internet Calendaring and Scheduling Core Object Specification" http://tools.ietf.org/html/rfc2445