Specifications include, but are not limited to: The Solution must have the ability to require payment at the time of registration. 7.2.2 The Solution must include preventative functions to avoid create of duplicate profiles. 7.2.3 The Solution must be able to handle unlimited user records. 7.2.4 The Solution must be available to all users via the web 24/7, including secure controlled access by staff for management functions.\ 7.2.5 The Solution must be user friendly for students, instructors and staff. Cite examples. 7.2.6 Guests must have the ability to peruse and search the online schedule of offerings without logging into the Solution. 7.3 Course/Class Management 7.3.1 The Solution must not limit the number of class/section offerings a program can offer. 7.3.2 The Solution must associate accounting codes with class costs and fees/prices. 7.3.3 The Solution must allow contact hours, CEUs, etc. to be tracked. 7.3.4 If courses are built in the Solution, the Solution must offer the ability to add/delete/revise course information. 7.4 Administrative Functions 7.4.1 The Solution must have role-based control options for staff access. 7.4.2 The Solution must be able to send automatic email confirmations. Indicate the type of confirmations sent (e.g. registration confirmation, waiting list status, instructor correspondence, registration reminders, other) 7.4.3 The Solution must provide a quick way to analyze whether to run or cancel a class. Describe