ICE
The Interactive Chapter Experience - ICE is a packaged product that compliments several iMIS modules such as customers and committees. ICE data is pulled directly from iMIS enabling a single database for member information which can be updated and managed through a web interface. ICE provides for changes to the membership processes and fees allowing customization of some areas and utilizes SSRS reporting to produce an unlimited number of web-enabled reports.
The ICE admin site is used to define specific settings and enables configuration for unique processes and scalability. It is important to follow the predefined steps to ensure that integration between ICE and iMIS is working properly. The ICE admin URL is your normal ICE url plus /Admin after /ICE/. Example: http://website.org/ICE/Admin
ICE is primarily comprised of rules, which are used to apply specific behaviors and conditions, and content blocks, which are used to leverage and re-use predefined code.
Once you log in, you will be taken to the ICE admin main page, which includes general system information. 
BEST PRACTICE: It is recommended that you navigate with your mouse as opposed to your "Back" button. To prevent possible web browser conflicts, it is recommended to view ICE with the latest versions of Firefox, Safari, and/or Chrome.
New ICE Implementations
It is important to recognize that ICE will potentially replace existing iMIS functionality. During the design phase of your ICE implementation, ensure that you have evaluated all existing activity based processes, Forms, Reports, SQL scripts, and any other manual processes that will no longer be needed. Consultants may also have to re-engineer some of the reports as a result of gaining more efficient filtering functionality from ICE. Keep in mind that ICE allows users to "save" their information while completing a form, thus potentially creating a blank field in the database. This may cause some reports to display unwanted information. Make sure you design those reports to filter on the correct parameter to display the information that is needed.
BEST PRACTICE: Due to the complex configuration and integration of ICE, it is recommended to have at least two separate instances, one for test and one for live. In order to keep the live database as "clean" and production ready as possible, consultants are advised to do the majority of set up in the live database, then refresh the test environment with live configuration. This will also ensure that unwanted configuration in test does not clutter the live environment. Part of the initial requirements gathering for ICE should include the URL for their live database to ensure that we have the necessary components to create the two instances.
This procedure must be performed on an application server that already contains a working installation of iMIS and ICE. Ensure that the person performing this procedure has access to the sa login and password for the SQL Server instance on which you intend to create.
The test ICE administration site is accessed by your browser at the following: http://website.org/TESTICE/ICE/Admin. Working with the client's technical team, the CSI development team will set up access to the web server as well as perform the initial installation of ICE, which includes numerous tables and views.
NOTE: If ICE has not been published to the internet, you may need to modify your host file. The host file is stored in the following location: %WINDIR%\SYSTEM32\drivers\etc\hosts.
You can open the host file with Notepad, however, do NOT save the file as a "txt" file.
The iMIS manager account has permissions to access this site. Other users can be added through the security module, covered in the Security section of this user guide.
Once you have navigated to the site, you will be prompted for a login. ICE logins are tied to iMIS user accounts. 