Specifications include, but are not limited to: Event Management System Shall show locations that are available for reservation. Shall have pictures of room and schematic when selecting location. Shall show equipment that is in the room. Shall display location map when selecting location. Shall allow customization of who can automatically reserve or request “room”. Shall allow customization of allowing certain individuals to book reservations for certain locations automatically. Shall allow customization of what locations can be reserved online. Shall allow requests for tours and viewing availability online. Shall allow for guests to request type of tour - educational, legislative, art, expert tour, etc. Shall send notification to Visitor Services (Dept) of a request for tour and ability to add detail to outlook calendar including virtual tour link and resources. Shall allow for request of specific locations in the capitol – galleria, rotunda, rooms, and public spaces, etc. Shall allow the ability to check availability online based on size and use requirements (conf vs. hearing room). Shall have role-based user groups with varied rights for accessing functions in the application. Shall allow special accommodations and equipment requests / needs when booking. Shall allow for request of video and/or web conferencing. Shall allow user to request information about future events happening in Capitol. Shall require approval for weekend and evening events – subject to approval and policies displayed upon request of reservation. Shall allow all reservations online – assumes online payment option. Shall accept online payments for fees. Shall allow changes to reservations online. Shall allow cancellation of reservations online. Shall notify Capitol staff of changes in reservations, including Fiscal Services for any refunds. Shall send an email confirmation of reservation. Shall send email confirmation of any changes to reservations to user. Shall send reservation/tour policies and use agreement with confirmation of reservation. Shall send receipt of payment received. Shall require billing information with reservation. Shall allow fees to be waived for internal users when reserving certain rooms. Shall allow changes to billing information online. Shall send notification of billing changes to original and person who changed to. Shall allow some events to be “private” – only show “reserved” to public without detail. Shall have user group rights for various functions in application. Shall have users assigned to user groups. Shall have private notes/comments on users. Shall allow public to set up and manage account online. Shall receive agendas and associate an agenda to meeting. Shall display and require acceptance of Capitol reservation policies specific to location reserving. Shall allow to request additional equipment for a room; special requests, e.g. “other”. Shall have equipment inventory tracking. Shall invoice for initial and additional fees. Shall cancel reservation if not paid prior to event happening. Shall have the ability to search for an event by description/name of event. Shall have the ability to search for user and current. Shall have the ability to see user account and prior reservations made by user. Shall have the ability to view events by location, by day, week, month. Shall have the ability to view events by type in a day, week, month. Shall send notification of events to tenants of the building. Shall send notifications to users of events happening in Capitol. Shall send email notifications to specific external stakeholders (OSP, City, etc.) of events happening. Shall issue work orders to other departments based on reservation requests. Shall send notification to other departments based on reservation requests. Shall have work order generated to Facilities. Shall have the ability to add/remove locations or change profiles of available locations to be reserved. Shall be able to make “block” reservations – series, reoccurrence. Shall send email notification to a specific distribution list if certain areas are reserved (i.e. front steps to City). Shall be customizable for locations to be reserved. Shall retain history of the reservations in a location. Shall retain history of all users. Shall allow export of any and all data. Shall have customizable reports. Shall have canned reports.