Laserfiche WebLink
<br />1- <br /> <br />and search features are managed by Granicus MediaManager, eliminating any manual website updates <br />for your meeting agenda and minutes information. Plus, it is easily accessible for your citizens! <br /> <br />1.3. Project Oveniew. Once a purchase order or signed contract has been received, a MCCi project manager will be <br />assigned to your project. It is the responsibility of your organization to assign a single point of contact for this <br />project. While more than one person can be involved in the process, a single point of contact for key issues is <br />important. Notify your MCCi account representative or project manager of the name of the point of contact. This <br />contact will be handled via conference calls and web conferencing. Your MCCi project manager will contact <br />your coordinator to run through the mockup and deployment process. <br /> <br />a. Pre-consultation. MCCi's Project Managcr will scnd the client our professional services document <br />requesting information pertaining to your implementation. This will include copies of your agenda item <br />request forms, agendas, minutes and any exiting documentation of your workflow/approval process. <br />This documentation will aid MCCi's Project Manager during the mock up phase and customization <br />phases. <br />. JAD Session. This is a service and is highly recommended. Description of lAD is included in the <br />standard services section (2.1 a). <br />b. Mockups. Each client has their own fonnat for board meeting agendas and minutes. Your MCCi Project <br />Manager will work with you to create mockup! that meet your unique needs. This process is handled via <br />teleconference calls. Meetings will focus on the layout of your current Agenda and then any changes you <br />wish to make to it. Once your needs are understood, MCCi will mock-up a sample Agenda for your <br />review. We will go through this mockup process until your needs are met and mock ups are approved. <br /> <br />c. Customiution. Once Mockups and Workflows are approved by )'ou, they will be turned over to MCCi <br />developers to create your specific layout. One developer will be assigned to build your layout to insure <br />continuity on the project. The customization time frame can vary based on current workload and the <br />complexity of your project, but typically within one month of mockup approval. <br /> <br />d. Demonstration & Pre-testing. Once customization is complete MCCi's project managcr will takc the <br />client through a complete demonstration of the product functionality and customizations. <br /> <br />e. Installation. Installation and testing should take no longer than 1 day. The client will have the option of <br />installing MuniAgenda in their live environment prior to training, or allowing MCCi to temporarily host <br />during training and malee necessary changes identified during mock agenda sessions. <br />Remote Installation: When circumstances aI/ow. instal/ation may be handled "remotely". <br /> <br />f. Trainin&. Training is conducted onsite and includes training the administrator and end-users. MCCi also <br />offers Train-the-trainer training if that is city/county protocol. In most deployments, training can be <br />accomplished ,vithin 2-3 days. MCCi also provides thc client with admin and user training manuals as <br />part of the software purchase for future reference. <br />Remote Training: When circumstances allow. training may be handled "remotely". <br /> <br />e. Parallel Testin&. Client agrees to run a parallel testing environment prior to attempting a "live" <br />MuniAgenda environment. Parallel testing is defined as running the current agenda process concurrently <br />with the new MuniAgenda process, until the client project team is comfortable moving forward into a <br />live environment. MCCi has seen the most success with clients who take the time to apply the parallel <br />concept prior to attempting a live MuniAgenda environment. Final Billing will occur prior to parallel <br />testing, but MCCi support is active and fulIy available during this period. <br /> <br />1.4. Sample Implementation Timeline. The following steps in the implementation process are based on MCCi <br />experiences and best practices. The overall timeframe may vary depending on the client's responsiveness. Days <br />below are calendar days. <br /> <br />SIB <br /> <br />C'i <br /> <br />6 <br />