Common use of General Assumptions Clause in Contracts

General Assumptions. To determine which platform/licenses are applicable, please refer to the Pricing section. The following assumptions serve as the basis for the Service Package(s) reflected below. Any service or activity not described below is not included in the Scope of services to be provided. Variations to the following may impact the Service Package’s cost and/or schedule justifying a change order. ▪ MCCi‘s completion of a Deliverable to Client shall constitute that MCCi has conducted its own review and believes it meets Client’s requirements. Client shall then have the right to conduct its own review of the Deliverable as Client deems necessary. If Client, in its reasonable discretion, determines that any submitted Deliverable does not meet the agreed upon expectations, Client shall have five (5) business days after MCCi’s submission to give written notice to MCCi specifying the deficiencies in reasonable detail. MCCi shall use reasonable efforts to promptly resolve any such deficiencies. Upon resolution of any such deficiencies, MCCi shall resubmit the Deliverable for review as set forth above. Notwithstanding the foregoing, if Client fails to reject any Deliverable within five (5) business days, such Deliverable shall be deemed accepted. ▪ If either party identifies a business issue during the project, MCCi and Client must jointly establish a plan to resolve the issues with potential impact analysis of timeline and budget within five (5) business days of identification. Any necessary business decision resulting from the identified business issues must be made by Client within five (5) business days from request. ▪ Client is responsible to ensure that adequate hardware/infrastructure is in place and capable of handling the extra resources that may be required to support the services performed. ▪ Any additional software licensing needs related to this service/process configuration have not been considered or included as part of service packages. Client is responsible for ensuring that the required software licensing is available. ▪ If the Services require MCCi to access or use any third party software products provided or used, Client warrants that it shall have all rights and licenses of third parties necessary or appropriate for MCCi to access or use such third party products and agrees to produce evidence of such rights and licenses upon the reasonable request of MCCi and to indemnify, hold harmless and defend MCCi from and against any claims, actions, demands, lawsuits, damages, liabilities, settlements, penalties, fines, costs and expenses (including reasonable attorneys’ fees) to the extent arising from MCCi’s access to or use of such third party products. ▪ Client will maintain primary contacts and project staff for the duration of the project, as a change in staff may result in a change order for time spent by MCCi on retraining, reeducating, or changes in direction. ▪ Through the course of this project, MCCi may choose to utilize the third-party service ▇▇▇▇▇ (▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇) for project management and team collaboration. Documentation and correspondence exchanged between ▇▇▇▇ and Client may be stored in Asana. ▪ Client will ensure that all Client’s personnel who may be necessary or appropriate for the successful performance of the services will, on reasonable notice: (i) be available to assist MCCi’ personnel by answering business, technical and operational questions and providing requested documents, guidelines and procedures in a timely manner; (ii) participate in the services as reasonably necessary; and (iii) be available to assist MCCi with any other activities or tasks required to complete the services. ▪ All Services pricing assumes the Client will grant MCCi unattended access to the required infrastructure for the project. Failure to provide this access will result in a Change Order increasing the cost to the Client and the timeline of the project. ▪ Projects enter “On-Hold” status when (i) Client requests a delay in starting a new project, or (ii) Client is unresponsive for more than 15 business days during an active project. On-Hold status will remain until a new project start date is mutually agreed upon, or until Closed. MCCi may elect to Close the project due to project remaining On-Hold for more than 35 business days. ▪ Projects that are Closed prior to completion, will be billed for any progress made to date and the MCCi project team will no longer be assigned to the project. Billing for progress made to date is based on the number of hours worked or the estimated percentage of the project that has been completed, whichever is greater. Subsequently, a new order is required to restart a Closed project, and to have new MCCi project resources assigned. ▪ Client will provide a single point of contact responsible for coordinating communications and scheduling amongst Client stakeholders. ▪ MCCi will conduct a project kickoff call with Client to set objectives and review systems/processes used. ▪ Google Chrome or Chrome Microsoft Edge is installed on all Laserfiche servers. ▪ TLS 1.2 is configured on all Laserfiche servers. ▪ Firewall ports will be opened for and unattended remote access on all necessary servers will be granted to MCCi. ▪ All services will be performed Monday – Friday, 8 am to 5 pm EST. ▪ MCCi will only provide recordings of trainings or meetings if requested in advance. Requested recordings will be available through the Training Center for Laserfiche. ▪ Client will acquire, install, and setup TLS certificates that meet application requirements. ▪ Purchase of Managed Cloud services may cover some of these assumptions/deliverables. ▪ Client will ensure previously agreed upon scheduled trainings are attended by their staff. For cancellations or rescheduling, the minimum notice period requirement to avoid penalties is 2 calendar weeks prior to the training date. Penalties: (i) Regardless of the notification time period, if the training was to be in person and MCCi has incurred non-refundable travel expenses, client will reimburse MCCi accordingly, and (ii) If client cancels or reschedules training within 7 calendar days and no less than 48 hours from the training date, the client will forfeit half of the allotted training time, or be assessed a fee equal to 50% of the training package purchased, or (ii) If the client cancels or reschedules the training within 48 hours of the training date, or is a no show on the training date, the training package purchased will be charged in full and forfeited by the client. ▪ Alpha Testing – Defined as internal acceptance testing performed by the project team prior to releasing the product or configuration to the Client ▪ Basic Deployment Testing – Defined as testing to ensure that the crucial functions of the system are operating properly and that the deployment is stable ▪ Beta Testing – Defined as the testing performed to verify functionality and fulfillment of user requirements ▪ User Acceptance Testing – Defined as testing performed by the Client’s users to verify and accept the implemented functionality or deployment ▪ MCCi is not responsible for assigning an external URL for any web-based platform/software module. ▪ MCCi is not responsible for creating or maintaining backups, backup plans or recovery plans. ▪ MCCi is not responsible for creating training documentation. ▪ MCCi is not responsible for final testing including, but not limited to, configuration changes made by Client prior to system handoff. ▪ Except where specifically noted, no custom coding is included; configuration work is restricted to the capabilities associated with the out-of-the-box solution. MCCi’s Laserfiche Repository Configuration Services are designed to assist the Client with establishing a basic repository structure. The goal is to start a foundation for the Client’s organization to build their Laserfiche repository from and help establish consistent standards the Client’s organizations can build on. ▇▇▇▇’s team will work with Client’s Project Manager to discover the templates and structure that fits the Client needs. ▪ Define each user and group necessary to access Laserfiche ▪ Complete requirements gathering with MCCi Project Team to define document types, naming schemes, folder paths, and metadata ▪ Provide requirements gathering ▪ Create up to two (2) folder structures that consist of three (3) tiered levels ▪ Create up to two (2) Laserfiche templates with up to seven (7) fields each ▪ Create up to two (2) Laserfiche User Groups ▪ Set entry access security for up to two-level ▪ Conduct one (1) session (three (3) hours total) of remote “train the trainer” training on Basic Laserfiche and User functions.

General Assumptions. To determine which platform/licenses are applicable, please refer to the Pricing section. The following assumptions serve as the basis for the Service Package(s) reflected below. Any service or activity not described below is not included in the Scope of services to be provided. Variations to the following may impact the Service Package’s cost and/or schedule schedule, justifying a change orderChange Order. ▪ MCCi‘s completion of a Deliverable to Client shall constitute that MCCi has conducted its own review and believes it meets Client’s requirements. Client shall then have the right to conduct its own review of the Deliverable as Client deems necessary. If Client, in its reasonable discretion, determines that any submitted Deliverable does not meet the agreed upon expectations, Client shall have five (5) business days after MCCi’s submission to give written notice to MCCi specifying the deficiencies in reasonable detail. MCCi shall use reasonable efforts to promptly resolve any such deficiencies. Upon resolution of any such deficiencies, MCCi shall resubmit the Deliverable for review as set forth above. Notwithstanding the foregoing, if Client fails to reject any Deliverable within five (5) business days, such Deliverable shall be deemed accepted. ▪ If either party identifies a business issue during the project, MCCi and Client must jointly establish a plan to resolve the issues with potential impact analysis of timeline and budget within five (5) business days of identification. Any necessary business decision resulting from the identified business issues must be made by Client within five (5) business days from request. ▪ Client is responsible to ensure for ensuring that adequate hardware/infrastructure is in place and capable of handling the extra resources that may be required to support the services performed. ▪ Any additional software software-licensing needs related to this service/process configuration have not been considered or included as part of service packages. Client is responsible for ensuring that the required software licensing is available. ▪ If the Services require MCCi to access or use any third party software products provided or used, Client warrants that it shall have all rights and licenses of third parties necessary or appropriate for MCCi to access or use such third party products and agrees to produce evidence of such rights and licenses upon the reasonable request of MCCi and to indemnify, hold harmless and defend MCCi from and against any claims, actions, demands, lawsuits, damages, liabilities, settlements, penalties, fines, costs and expenses (including reasonable attorneys’ fees) to the extent arising from MCCi’s access to or use of such third party products. ▪ Client will maintain primary contacts and project staff for the duration of the project, as a change in staff may result in a change order Change Order for time spent by MCCi on retraining, reeducating, or changes in direction. ▪ Through the course of this project, MCCi may choose to utilize the third-party service ▇▇▇▇▇ (▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇) for project management and team collaboration. Documentation and correspondence exchanged between ▇▇▇▇ and Client may be stored in Asana. ▪ Client will ensure that all Client’s personnel who may be necessary or appropriate for the successful performance of the services will, on reasonable notice: (i) be available to assist MCCi’ personnel by answering business, technical and operational questions and providing requested documents, guidelines and procedures in a timely manner; (ii) participate in the services as reasonably necessary; and (iii) be available to assist MCCi with any other activities or tasks required to complete the services. ▪ All Services pricing assumes the Client will grant MCCi unattended access to the required infrastructure for the project. Unattended access requires the following: ▪ Either a VPN connection with proper credentials or installation of on-demand remote access software utilized by MCCi. ▪ Connections that can be made by an assigned MCCi Project Team without intervention from the Client from the hours of 8:00 AM ET to 8:00 PM ET. ▪ A Windows Domain account assigned exclusively to the assigned MCCi Project Team that has administrative access to all infrastructure being serviced for purposes of the project. ▪ A Windows Domain account, and complete access to that account including the password, for the service account to be used with any installed software products. Failure to provide this access will result in a Change Order increasing the cost to the Client and the timeline of the project. ▪ Projects enter “On-Hold” status when (i) Client requests a delay in starting a new project, or (ii) Client is unresponsive for more than 15 business days during an active project. On-Hold status will remain until a new project start date is mutually agreed upon, or until Closed. MCCi may elect to Close the project due to project remaining On-Hold for more than 35 business days. ▪ Projects that are Closed prior to completion, will be billed for any progress made to date and the MCCi project team will no longer be assigned to the project. Billing for progress made to date is based on the number of hours worked or the estimated percentage of the project that has been completed, whichever is greater. Subsequently, a new order is required to restart a Closed project, and to have new MCCi project resources assigned. ▪ Client will provide a single point of contact responsible for coordinating communications and scheduling amongst Client stakeholders. ▪ MCCi will conduct a project kickoff call with Client to set objectives and review systems/processes used. ▪ Google Chrome or Chrome Microsoft Edge is installed on all Laserfiche servers. ▪ TLS 1.2 is configured on all Laserfiche servers. ▪ Firewall ports will be opened for and unattended remote access on all necessary servers will be granted to MCCi. ▪ All services will be performed Monday – Friday, 8 am to 5 pm EST. ▪ MCCi will only provide recordings of trainings or meetings if requested in advance. Requested recordings will be available through the Training Center for Laserfiche. ▪ Client will acquire, install, and setup set up TLS certificates that meet application requirements. ▪ Purchase of Managed Cloud services may cover some of these assumptions/deliverables. ▪ Client will ensure previously agreed upon scheduled trainings are attended by their staff. For cancellations or rescheduling, the minimum notice period requirement to avoid penalties is 2 calendar weeks prior to the training date. Penalties: (i) Regardless of the notification time period, if the training was to be in person and MCCi has incurred non-refundable travel expenses, client will reimburse MCCi accordingly, and (ii) If client cancels or reschedules training within 7 calendar days and no less than 48 hours from the training date, the client will forfeit half of the allotted training time, or be assessed a fee equal to 50% of the training package purchased, or (ii) If the client cancels or reschedules the training within 48 hours of the training date, or is a no show on the training date, the training package purchased will be charged in full and forfeited by the client. ▪ Alpha Testing – Defined as internal acceptance testing performed by the project team prior to releasing the product or configuration to the Client ▪ Basic Deployment Testing – Defined as testing to ensure that the crucial functions of the system are operating properly and that the deployment is stable ▪ Beta Testing – Defined as the testing performed to verify functionality and fulfillment of user requirements ▪ User Acceptance Testing – Defined as testing performed by the Client’s users to verify and accept the implemented functionality or deployment ▪ MCCi is not responsible for assigning an external URL for any web-based platform/software module. ▪ MCCi is not responsible for creating or maintaining backups, backup plans or recovery plans. ▪ MCCi is not responsible for creating training documentation. ▪ MCCi is not responsible for final testing including, but not limited to, configuration changes made by Client prior to system handoff. ▪ Except where specifically noted, no custom coding is included; configuration work is restricted to the capabilities associated with the out-of-the-box solution. MCCi’s Laserfiche Repository Filing Workflow Configuration Services are designed to assist the Client with establishing a basic repository structurebe highly collaborative. The goal is to start provide a foundation for the customized process that allows Client’s organization to build their Laserfiche repository from archive specified records in a proper format and help establish location that is consistent standards the with Client’s organizations can build onorganization’s standards. To execute, ▇▇▇▇’s team of expert Project Managers and System Engineers will work with Client’s Project Manager to discover the templates and structure that fits the Client needsbuild a Filing Workflow in Client’s Laserfiche environment. ▪ Define each user and group necessary to access Laserfiche ▪ Complete requirements gathering with MCCi Project Team Manager to define document types, naming schemes, folder paths, and metadata ▪ Provide requirements gathering Configure a Laserfiche Filing Workflow to file documents in the Laserfiche repository (not to exceed 15 document types) ▪ Rename documents and route to appropriate folder structure ▪ Create up to two (2) folder structures that consist of three (3) tiered levels ▪ Create up to two (2) Laserfiche templates with and up to seven (7) fields each per template ▪ Create up to two (2) Laserfiche User Groups Provide requirements gathering ▪ Set entry access security for up to tworoot-level security ▪ Conduct one (1) session (three (3) hours total) half-day of remote “train the trainer” training on Basic administering and executing the processes built by the MCCi project team ▪ Perform alpha and beta testing on the built processes. MCCi will transition project to Client UAT team once beta is complete and successful MCCi is not responsible for the following: ▪ Configuring business routing logic ▪ Restructuring metadata ▪ Determining Records Management settings ▪ Cleaning up existing documents ▪ Configuring automated security ▪ Installing software ▪ Workflow is already installed and configured. MCCi’s Quick Fields basic configuration package is designed for MCCi to install Laserfiche Quick Fields, configure a single desired Quick Fields session with one classification type, configure real-time lookup, and User functionscreate a corresponding Laserfiche Template and fields. ▪ Provide lookup credentials ▪ Format Client forms in a manner that is conducive to QF indexing. Client may need to change the format of forms for all functionality to work consistently. ▪ Install Quick Fields ▪ Configure one (1) Quick Fields session ▪ Set up one (1) session classification and lookup using Real-Time Lookup ▪ Provide Lookup which allows for one (1) ODBC connection and one (1) field data query ▪ Create one (1) Laserfiche Template with up to seven (7) fields MCCi is not responsible for the following: ▪ Configuring Workflow ▪ Creating dynamic fields ▪ Providing Quick Fields training ▪ Client has procured appropriate licensing for Real-Time Lookup. MCCi will manage the work, communication, and documentation MCCi deems necessary for successful project delivery. ▪ Manage Client communication ▪ Produce project documentation ▪ Oversee risk/issue management ▪ Oversee meeting scheduling ▪ Ensure deliverables are met ▪ Budgeting and Resource Management As Client’s first-tier solution provider, MCCi provides multiple options for technical support. Client’s annual renewal covers application break/fix support, version downloads, and continued educational resources. MCCi offers supplemental support packages to cover remote training, basic configuration services, and maintenance of existing business processes. MCCi’s Managed Support Services (MMSS) or Process Administration Support Services (MPASS & MPASS2) packages are strongly encouraged to be included with every renewal. Supplemental Support Packages are annual subscriptions and pricing is based on the package purchased and an advanced discounted block of hours, which expire on the same date as Client’s annual renewal. MMSS pricing for the advanced block of hours is based on MCCi’s Support Technician II hourly rate discounted by 10%. MPASS and MPASS2 pricing for the advanced block of hours is based on MCCi’s Application Support Analyst hourly rate discounted by 10%. Configuration and maintenance of basic business processes and MCCi packaged solution utilizing Laserfiche Forms and Workflow Maintenance of MCCi/Client configured complex business processes ** Hours: MCCi allows clients to use their hours for a multitude of services, if a request will not start a service that cannot be completed with the hours available. None of the packages listed above are intended to be utilized to configure a new complex business process. In those instances, a separate SOW is required. ▪ For self-hosted (applications hosted by Client) solutions: Configuring/maintaining backups and any general network, security, or operating system settings outside of Client’s solution. ▪ Managing application-level security. ▪ Managing and creating retention policies related to Records Management Module. ▪ Providing an IT contact (internal or third-party) for MCCi to work with as necessary. ▪ Providing remote access capabilities as needed. If the Client requests MCCi to have unattended access, the Client assumes all responsibility for the related session(s). The Client will work with MCCi to set up user profiles, user tags, etc. to allow desired security rights/access. ▪ Creating/providing process diagrams (and any other necessary paperwork/examples).

General Assumptions. To determine which platform/licenses are applicable, please refer to the Pricing section. The following assumptions serve as the basis for the Service Package(s) reflected below. Any service or activity not described below is not included in the Scope of services to be provided. Variations to the following may impact the Service Package’s cost and/or schedule schedule, justifying a change orderChange Order. ▪ MCCi‘s completion of a Deliverable to Client shall constitute that MCCi has conducted its own review and believes it meets Client’s requirements. Client shall then have the right to conduct its own review of the Deliverable as Client deems necessary. If Client, in its reasonable discretion, determines that any submitted Deliverable does not meet the agreed upon expectations, Client shall have five (5) business days after MCCi’s submission to give written notice to MCCi specifying the deficiencies in reasonable detail. MCCi shall use reasonable efforts to promptly resolve any such deficiencies. Upon resolution of any such deficiencies, MCCi shall resubmit the Deliverable for review as set forth above. Notwithstanding the foregoing, if Client fails to reject any Deliverable within five (5) business days, such Deliverable shall be deemed accepted. ▪ If either party identifies a business issue during the project, MCCi and Client must jointly establish a plan to resolve the issues with potential impact analysis of timeline and budget within five (5) business days of identification. Any necessary business decision resulting from the identified business issues must be made by Client within five (5) business days from request. ▪ Client is responsible to ensure for ensuring that adequate hardware/infrastructure is in place and capable of handling the extra resources that may be required to support the services performed. ▪ Any additional software software-licensing needs related to this service/process configuration have not been considered or included as part of service packages. Client is responsible for ensuring that the required software licensing is available. ▪ If the Services require MCCi to access or client data, item, and/or use any third party software products provided or used, Client represents and warrants that it shall have all rights and licenses licenses, including, without limitation those of third parties parties, necessary or appropriate for MCCi to access or use such data and/ or third party products and agrees to produce evidence of such rights and licenses upon the reasonable request of MCCi and to indemnify, hold harmless and defend MCCi from and against any claims, actions, demands, lawsuits, damages, liabilities, settlements, penalties, fines, costs and expenses (including reasonable attorneys’ fees) to the extent arising from MCCi’s access to or use of such third party products. ▪ Client will maintain primary contacts and project staff for the duration of the project, as a change in staff may result in a change order Change Order for time spent by MCCi on retraining, reeducating, or changes in direction. ▪ Through the course of this project, MCCi may choose to utilize the third-party service ▇▇▇▇▇ (▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇) for project management and team collaboration. Documentation and correspondence exchanged between ▇▇▇▇ and Client may be stored in Asana. ▪ Client will ensure that all Client’s personnel who may be necessary or appropriate for the successful performance of the services will, on reasonable notice: (i) be available to assist MCCi’ personnel by answering business, technical and operational questions and providing requested documents, guidelines and procedures in a timely manner; (ii) participate in the services as reasonably necessary; and (iii) be available to assist MCCi with any other activities or tasks required to complete the services. ▪ All Services pricing assumes the Client will grant MCCi secure unattended access to the required infrastructure for the project. Unattended access requires the following: ▪ Either a VPN connection with proper credentials or installation of on-demand remote access software utilized by MCCi. ▪ Connections that can be made by an assigned MCCi Project Team without intervention from the Client from the hours of 8:00 AM ET to 8:00 PM ET. ▪ A Windows Domain account assigned exclusively to the assigned MCCi Project Team, with passwords provided, that has administrative access to all infrastructure being serviced for purposes of the project. ▪ A Windows Domain account, and complete access to that account including the password, for the service account to be used with any installed software products. ▪ Failure to provide this access will result in a Change Order increasing the cost to the Client and the timeline of the project. ▪ Projects enter “On-Hold” status when (i) Client requests a delay in starting a new project, or (ii) Client is unresponsive for more than 15 business days during an active project. On-Hold status will remain until a new project start date is mutually agreed upon, or until Closed. MCCi may elect to Close the project due to project remaining On-Hold for more than 35 business days. ▪ Projects that are Closed prior to completion, will be billed for any progress made to date and the MCCi project team will no longer be assigned to the project. Billing for progress made to date is based on the number of hours worked or the estimated percentage of the project that has been completed, whichever is greater. Subsequently, a new order is required to restart a Closed project, and to have new MCCi project resources assigned. ▪ Client will provide a single point of contact responsible for coordinating communications and scheduling amongst Client stakeholders. ▪ MCCi will conduct a project kickoff call with Client to set objectives and review systems/processes used. ▪ Google Chrome or Chrome Microsoft Edge is installed on all Laserfiche servers. ▪ TLS 1.2 is configured on all Laserfiche servers. ▪ Firewall ports will be opened for and unattended remote access on all necessary servers will be granted to MCCi. ▪ All services will be performed Monday – Friday, 8 am to 5 pm EST. ▪ MCCi will only provide recordings of trainings or meetings if requested in advance. Requested recordings will be available through the Training Center for Laserfiche. ▪ Client will acquire, install, and setup set up TLS certificates that meet application requirements. ▪ Purchase of Managed Cloud services may cover some of these assumptions/deliverables. ▪ Client will ensure previously agreed upon scheduled trainings are attended by their staff. For cancellations or rescheduling, the minimum notice period requirement to avoid penalties is 2 calendar weeks prior to the training date. Penalties: (i) Regardless of the notification time period, if the training was to be in person and MCCi has incurred non-refundable travel expenses, client will reimburse MCCi accordingly, and (ii) If client cancels or reschedules training within 7 calendar days and no less than 48 hours from the training date, the client will forfeit half of the allotted training time, or be assessed a fee equal to 50% of the training package purchased, or (ii) If the client cancels or reschedules the training within 48 hours of the training date, or is a no show on the training date, the training package purchased will be charged in full and forfeited by the client. ▪ Alpha Testing – Defined as internal acceptance testing performed by the project team prior to releasing the product or configuration to the Client ▪ Basic Deployment Testing – Defined as testing to ensure that the crucial functions of the system are operating properly properly, and that the deployment is stable ▪ Beta Testing – Defined as the testing performed to verify functionality and fulfillment of user requirements ▪ User Acceptance Testing – Defined as testing performed by the Client’s users to verify and accept the implemented functionality or deployment ▪ MCCi is not responsible for assigning an external URL for any web-based platform/software module. ▪ MCCi is not responsible for creating or maintaining backups, backup plans or recovery plans. ▪ MCCi is not responsible for creating training documentation. ▪ MCCi is not responsible for final testing including, but not limited to, configuration changes made by Client prior to system handoff. ▪ Except where specifically noted, no custom coding is included; configuration work is restricted to the capabilities associated with the out-of-the-box solution. MCCi’s Laserfiche Repository Filing Workflow Configuration Services are designed to assist the Client with establishing a basic repository structurebe highly collaborative. The goal is to start provide a foundation for the customized process that allows Client’s organization to build their Laserfiche repository from archive specified records in a proper format and help establish location that is consistent standards the with Client’s organizations can build onorganization’s standards. ▇▇▇▇To execute, MCCi’s team of expert Project Managers and System Engineers will work with Client’s Project Manager to discover the templates and structure that fits the Client needsbuild a Filing Workflow in Client’s Laserfiche environment. ▪ Define each user and group necessary to access Laserfiche ▪ Complete requirements gathering with MCCi Project Team Manager to define document types, naming schemes, folder paths, and metadata ▪ Provide requirements gathering Configure a Laserfiche Filing Workflow to file documents in the Laserfiche repository (not to exceed 15 document types) ▪ Rename documents and route to appropriate folder structure ▪ Create up to two (2) folder structures that consist of three (3) tiered levels ▪ Create up to two (2) Laserfiche templates with and up to seven (7) fields each per template ▪ Create up to two (2) Laserfiche User Groups Provide requirements gathering ▪ Set entry access security for up to tworoot-level security ▪ Conduct one (1) session (three (3) hours total) half-day of remote “train the trainer” training on Basic administering and executing the processes built by the MCCi project team ▪ Perform alpha and beta testing on the built processes. MCCi will transition project to Client UAT team once beta is complete and successful MCCi is not responsible for the following: ▪ Configuring business routing logic ▪ Restructuring metadata ▪ Determining Records Management settings ▪ Cleaning up existing documents ▪ Configuring automated security ▪ Installing software ▪ Workflow is already installed and configured. MCCi’s Quick Fields basic configuration package is designed for MCCi to install Laserfiche Quick Fields, configure a single desired Quick Fields session with one classification type, configure real-time lookup, and create a corresponding Laserfiche Template and fields. ▪ Provide lookup credentials ▪ Format Client forms in a manner that is conducive to QF indexing. Client may need to change the format of forms for all functionality to work consistently. ▪ Install Quick Fields ▪ Configure one (1) Quick Fields session ▪ Set up one (1) session classification and lookup using Real-Time Lookup ▪ Provide Lookup which allows for one (1) ODBC connection and one (1) field data query ▪ Create one (1) Laserfiche Template with up to seven (7) fields MCCi is not responsible for the following: ▪ Configuring Workflow ▪ Creating dynamic fields ▪ Providing Quick Fields training ▪ Client has procured appropriate licensing for Real-Time Lookup. MCCi’s User functionsOverview Training is a great introduction to the Laserfiche repository, which is accessed through an application called the Laserfiche Client or the Laserfiche Cloud site. This training is specifically designed to provide new Laserfiche Clients with the ability to better understand Laserfiche before the discovery process. Attendees will become familiar with the Laserfiche repository organization best practices, understanding templates and how to search and retrieve existing content. Training is conducted on the web-based client and your trainer can emphasize certain topics listed below. ▪ User Navigation ▪ Search & Retrieval ▪ Metadata ▪ Import Options ▪ Repository Organization ▪ Export Options ▪ Brief RME Review (If Applicable) ▪ Provide one (1) training session for 1.5 hours (90 Min) ▪ Provide Laserfiche Overview Training on MCCi Environment ▪ Provide training for up to fifteen (15) users per session ▪ Training will be provided remotely on a MCCi Environment ▪ This is intended to occur prior to discovery to assist in the effectiveness of solution design ▪ This is not a replacement for Laserfiche End User Training ▪ The client will not have hands-on access to a Laserfiche environment ▪ MCCi is not responsible for customizing training materials for the client. MCCi will manage the work, communication, and documentation MCCi deems necessary for successful project delivery. ▪ Manage Client communication ▪ Produce project documentation ▪ Oversee risk/issue management ▪ Oversee meeting scheduling ▪ Ensure deliverables are met Budgeting and Resource Management As Client’s first-tier solution provider, MCCi provides multiple options for technical support. Client’s annual renewal covers application break/fix support, version downloads, and continued educational resources. MCCi offers supplemental support packages to cover remote training, basic configuration services, and maintenance of existing business processes. MCCi’s Managed Support Services (MMSS) or Process Administration Support Services (MPASS & MPASS2) packages are strongly encouraged to be included with every renewal. Supplemental Support Packages are annual subscriptions and pricing is based on the package purchased and an advanced discounted block of hours, which expire on the same date as Client’s annual renewal. MMSS pricing for the advanced block of hours is based on MCCi’s Support Technician II hourly rate discounted by 10%. MPASS and MPASS2 pricing for the advanced block of hours is based on MCCi’s Application Support Analyst hourly rate discounted by 10%. Configuration and maintenance of basic business processes and MCCi packaged solution utilizing Laserfiche Forms and Workflow Maintenance of MCCi/Client configured complex business processes ** Hours: MCCi allows clients to use their hours for a multitude of services, if a request will not start a service that cannot be completed with the hours available. None of the packages listed above are intended to be utilized to configure a new complex business process. In those instances, a separate SOW is required. ▪ For self-hosted (applications hosted by Client) solutions: Configuring/maintaining backups and any general network, security, or operating system settings outside of Client’s solution. ▪ Managing application-level security. ▪ Managing and creating retention policies related to Records Management Module. ▪ Providing an IT contact (internal or third-party) for MCCi to work with as necessary. ▪ Providing remote access capabilities as needed. If the Client requests MCCi to have unattended access, the Client assumes all responsibility for the related session(s). The Client will work with MCCi to set up user profiles, user tags, etc. to allow desired security rights/access. ▪ Creating/providing process diagrams (and any other necessary paperwork/examples).

General Assumptions. To determine which platform/licenses are applicable, please refer to the Pricing section. The following assumptions serve as the basis for the Service Package(s) reflected below. Any service or activity not described below is not included in the Scope of services to be provided. Variations to the following may impact the Service Package’s cost and/or schedule schedule, justifying a change orderChange Order. ▪ MCCi‘s completion of a Deliverable to Client shall constitute that MCCi has conducted its own review and believes it meets Client’s requirements. Client shall then have the right to conduct its own review of the Deliverable as Client deems necessary. If Client, in its reasonable discretion, determines that any submitted Deliverable does not meet the agreed upon expectations, Client shall have five (5) business days after MCCi’s submission to give written notice to MCCi specifying the deficiencies in reasonable detail. MCCi shall use reasonable efforts to promptly resolve any such deficiencies. Upon resolution of any such deficiencies, MCCi shall resubmit the Deliverable for review as set forth above. Notwithstanding the foregoing, if Client fails to reject any Deliverable within five (5) business days, such Deliverable shall be deemed accepted. ▪ If either party identifies a business issue during the project, MCCi and Client must jointly establish a plan to resolve the issues with potential impact analysis of timeline and budget within five (5) business days of identification. Any necessary business decision resulting from the identified business issues must be made by Client within five (5) business days from request. ▪ Client is responsible to ensure for ensuring that adequate hardware/infrastructure is in place and capable of handling the extra resources that may be required to support the services performed. ▪ Any additional software software-licensing needs related to this service/process configuration have not been considered or included as part of service packages. Client is responsible for ensuring that the required software licensing is available. ▪ If the Services require MCCi to access or client data, item, and/or use any third party software products provided or used, Client represents and warrants that it shall have all rights and licenses licenses, including, without limitation those of third parties parties, necessary or appropriate for MCCi to access or use such data and/ or third party products and agrees to produce evidence of such rights and licenses upon the reasonable request of MCCi and to indemnify, hold harmless and defend MCCi from and against any claims, actions, demands, lawsuits, damages, liabilities, settlements, penalties, fines, costs and expenses (including reasonable attorneys’ fees) to the extent arising from MCCi’s access to or use of such third party products. ▪ Client will maintain primary contacts and project staff for the duration of the project, as a change in staff may result in a change order Change Order for time spent by MCCi on retraining, reeducating, or changes in direction. ▪ Through the course of this project, MCCi may choose to utilize the third-party service ▇▇▇▇▇ (▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇) for project management and team collaboration. Documentation and correspondence exchanged between ▇▇▇▇ and Client may be stored in Asana. ▪ Client will ensure that all Client’s personnel who may be necessary or appropriate for the successful performance of the services will, on reasonable notice: (i) be available to assist MCCi’ personnel by answering business, technical and operational questions and providing requested documents, guidelines and procedures in a timely manner; (ii) participate in the services as reasonably necessary; and (iii) be available to assist MCCi with any other activities or tasks required to complete the services. ▪ All Services pricing assumes the Client will grant MCCi secure unattended access to the required infrastructure for the project. Unattended access requires the following: ▪ Either a VPN connection with proper credentials or installation of on-demand remote access software utilized by MCCi. ▪ Connections that can be made by an assigned MCCi Project Team without intervention from the Client from the hours of 8:00 AM ET to 8:00 PM ET. ▪ A Windows Domain account assigned exclusively to the assigned MCCi Project Team, with passwords provided, that has administrative access to all infrastructure being serviced for purposes of the project. ▪ A Windows Domain account, and complete access to that account including the password, for the service account to be used with any installed software products. ▪ Failure to provide this access will result in a Change Order increasing the cost to the Client and the timeline of the project. ▪ Projects enter “On-Hold” status when (i) Client requests a delay in starting a new project, or (ii) Client is unresponsive for more than 15 business days during an active project. On-Hold status will remain until a new project start date is mutually agreed upon, or until Closed. MCCi may elect to Close the project due to project remaining On-Hold for more than 35 business days. ▪ Projects that are Closed prior to completion, will be billed for any progress made to date and the MCCi project team will no longer be assigned to the project. Billing for progress made to date is based on the number of hours worked or the estimated percentage of the project that has been completed, whichever is greater. Subsequently, a new order is required to restart a Closed project, and to have new MCCi project resources assigned. ▪ Client will provide a single point of contact responsible for coordinating communications and scheduling amongst Client stakeholders. ▪ MCCi will conduct a project kickoff call with Client to set objectives and review systems/processes used. ▪ Google Chrome or Chrome Microsoft Edge is installed on all Laserfiche servers. ▪ TLS 1.2 is configured on all Laserfiche servers. ▪ Firewall ports will be opened for and unattended remote access on all necessary servers will be granted to MCCi. ▪ All services will be performed Monday – Friday, 8 am to 5 pm EST. ▪ MCCi will only provide recordings of trainings or meetings if requested in advance. Requested recordings will be available through the Training Center for Laserfiche. ▪ Client will acquire, install, and setup set up TLS certificates that meet application requirements. ▪ Purchase of Managed Cloud services may cover some of these assumptions/deliverables. ▪ Client will ensure previously agreed upon scheduled trainings are attended by their staff. For cancellations or rescheduling, the minimum notice period requirement to avoid penalties is 2 calendar weeks prior to the training date. Penalties: (i) Regardless of the notification time period, if the training was to be in person and MCCi has incurred non-refundable travel expenses, client will reimburse MCCi accordingly, and (ii) If client cancels or reschedules training within 7 calendar days and no less than 48 hours from the training date, the client will forfeit half of the allotted training time, or be assessed a fee equal to 50% of the training package purchased, or (ii) If the client cancels or reschedules the training within 48 hours of the training date, or is a no show on the training date, the training package purchased will be charged in full and forfeited by the client. ▪ Alpha Testing – Defined as internal acceptance testing performed by the project team prior to releasing the product or configuration to the Client ▪ Basic Deployment Testing – Defined as testing to ensure that the crucial functions of the system are operating properly properly, and that the deployment is stable ▪ Beta Testing – Defined as the testing performed to verify functionality and fulfillment of user requirements ▪ User Acceptance Testing – Defined as testing performed by the Client’s users to verify and accept the implemented functionality or deployment ▪ MCCi is not responsible for assigning an external URL for any web-based platform/software module. ▪ MCCi is not responsible for creating or maintaining backups, backup plans or recovery plans. ▪ MCCi is not responsible for creating training documentation. ▪ MCCi is not responsible for final testing including, but not limited to, configuration changes made by Client prior to system handoff. ▪ Except where specifically noted, no custom coding is included; configuration work is restricted to the capabilities associated with the out-of-the-box solution. MCCi’s Laserfiche Repository Configuration Services are designed to assist the Client with establishing a basic repository structure. The goal is to start a foundation for the Client’s organization to build their Laserfiche repository from and help establish consistent standards the Client’s organizations can build on. ▇▇▇▇MCCi’s team will work with Client’s Project Manager to discover the templates and structure that fits the Client needs. ▪ Define each user and group necessary to access Laserfiche ▪ Complete requirements gathering with MCCi Project Team to define document types, naming schemes, folder paths, and metadata ▪ Provide requirements gathering ▪ Create up to two (2) folder structures that consist of three (3) tiered levels with no more than ten (10) folders in each level ▪ Create up to two (2) Laserfiche templates with up to seven (7) fields each ▪ Create up to two (2) Laserfiche User Groups ▪ Set entry access security for up to two folder levels with no more than ten (10) folders in each level, for up to two-level ▪ Conduct one (1) session (three (3) hours total) of remote “train the trainer” training on Basic Laserfiche and User functions.

General Assumptions. To determine which platform/licenses are applicable, please refer to the Pricing section. The following assumptions serve as the basis for the Service Package(s) reflected below. Any service or activity not described below is not included in the Scope of services to be provided. Variations to the following may impact the Service Package’s cost and/or schedule justifying a change order. ▪ MCCi‘s completion of a Deliverable to Client shall constitute that MCCi has conducted its own review and believes it meets Client’s requirements. Client shall then have the right to conduct its own review of the Deliverable as Client deems necessary. If Client, in its reasonable discretion, determines that any submitted Deliverable does not meet the agreed upon expectations, Client shall have five (5) business days after MCCi’s submission to give written notice to MCCi specifying the deficiencies in reasonable detail. MCCi shall use reasonable efforts to promptly resolve any such deficiencies. Upon resolution of any such deficiencies, MCCi shall resubmit the Deliverable for review as set forth above. Notwithstanding the foregoing, if Client fails to reject any Deliverable within five (5) business days, such Deliverable shall be deemed accepted. ▪ If either party identifies a business issue during the project, MCCi and Client must jointly establish a plan to resolve the issues with potential impact analysis of timeline and budget within five (5) business days of identification. Any necessary business decision resulting from the identified business issues must be made by Client within five (5) business days from request. ▪ Client is responsible to ensure that adequate hardware/infrastructure is in place and capable of handling the extra resources that may be required to support the services performed. ▪ Any additional software licensing needs related to this service/process configuration have not been considered or included as part of service packages. Client is responsible for ensuring that the required software licensing is available. ▪ If the Services require MCCi to access or use any third party software products provided or used, Client warrants that it shall have all rights and licenses of third parties necessary or appropriate for MCCi to access or use such third party products and agrees to produce evidence of such rights and licenses upon the reasonable request of MCCi and to indemnify, hold harmless and defend MCCi from and against any claims, actions, demands, lawsuits, damages, liabilities, settlements, penalties, fines, costs and expenses (including reasonable attorneys’ fees) to the extent arising from MCCi’s access to or use of such third party products. ▪ Client will maintain primary contacts and project staff for the duration of the project, as a change in staff may result in a change order for time spent by MCCi on retraining, reeducating, or changes in direction. ▪ Through the course of this project, MCCi may choose to utilize the third-party service ▇▇▇▇▇ (▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇) for project management and team collaboration. Documentation and correspondence exchanged between ▇▇▇▇ and Client may be stored in Asana. ▪ Client will ensure that all Client’s personnel who may be necessary or appropriate for the successful performance of the services will, on reasonable notice: (i) be available to assist MCCi’ personnel by answering business, technical and operational questions and providing requested documents, guidelines and procedures in a timely manner; (ii) participate in the services as reasonably necessary; and (iii) be available to assist MCCi with any other activities or tasks required to complete the services. ▪ All Services pricing assumes the Client will grant MCCi unattended access to the required infrastructure for the project. Failure to provide this access will result in a Change Order increasing the cost to the Client and the timeline of the project. ▪ Projects enter “On-Hold” status when (i) Client requests a delay in starting a new project, or (ii) Client is unresponsive for more than 15 business days during an active project. On-Hold status will remain until a new project start date is mutually agreed upon, or until Closed. MCCi may elect to Close the project due to project remaining On-Hold for more than 35 business days. ▪ Projects that are Closed prior to completion, will be billed for any progress made to date and the MCCi project team will no longer be assigned to the project. Billing for progress made to date is based on the number of hours worked or the estimated percentage of the project that has been completed, whichever is greater. Subsequently, a new order is required to restart a Closed project, and to have new MCCi project resources assigned. ▪ Client will provide a single point of contact responsible for coordinating communications and scheduling amongst Client stakeholders. ▪ MCCi will conduct a project kickoff call with Client to set objectives and review systems/processes used. ▪ Google Chrome or Chrome Microsoft Edge is installed on all Laserfiche servers. ▪ TLS 1.2 is configured on all Laserfiche servers. ▪ Firewall ports will be opened for and unattended remote access on all necessary servers will be granted to MCCi. ▪ All services will be performed Monday – Friday, 8 am to 5 pm EST. ▪ MCCi will only provide recordings of trainings or meetings if requested in advance. Requested recordings will be available through the Training Center for Laserfiche. ▪ Client will acquire, install, and setup TLS certificates that meet application requirements. ▪ Purchase of Managed Cloud services may cover some of these assumptions/deliverables. ▪ Client will ensure previously agreed upon scheduled trainings are attended by their staff. For cancellations or rescheduling, the minimum notice period requirement to avoid penalties is 2 calendar weeks prior to the training date. Penalties: (i) Regardless of the notification time period, if the training was to be in person and MCCi has incurred non-refundable travel expenses, client will reimburse MCCi accordingly, and (ii) If client cancels or reschedules training within 7 calendar days and no less than 48 hours from the training date, the client will forfeit half of the allotted training time, or be assessed a fee equal to 50% of the training package purchased, or (ii) If the client cancels or reschedules the training within 48 hours of the training date, or is a no show on the training date, the training package purchased will be charged in full and forfeited by the client. ▪ Alpha Testing – Defined as internal acceptance testing performed by the project team prior to releasing the product or configuration to the Client ▪ Basic Deployment Testing – Defined as testing to ensure that the crucial functions of the system are operating properly properly, and that the deployment is stable ▪ Beta Testing – Defined as the testing performed to verify functionality and fulfillment of user requirements ▪ User Acceptance Testing – Defined as testing performed by the Client’s users to verify and accept the implemented functionality or deployment ▪ MCCi is not responsible for assigning an external URL for any web-based platform/software module. ▪ MCCi is not responsible for creating or maintaining backups, backup plans or recovery plans. ▪ MCCi is not responsible for creating training documentation. ▪ MCCi is not responsible for final testing including, but not limited to, configuration changes made by Client prior to system handoff. ▪ Except where specifically noted, no custom coding is included; configuration work is restricted to the capabilities associated with the out-of-the-box solution. MCCi’s Laserfiche Repository Configuration Services are designed to assist the Client with establishing a basic repository structure. The goal is to start a foundation for the Client’s organization to build their Laserfiche repository from and help establish consistent standards the Client’s organizations can build on. ▇▇▇▇’s team will work with Client’s Project Manager to discover the templates and structure that fits the Client needs. ▪ Define each user and group necessary to access Laserfiche ▪ Complete requirements gathering with MCCi Project Team to define document types, naming schemes, folder paths, and metadata ▪ Provide requirements gathering ▪ Create up to two (2) folder structures that consist of three (3) tiered levels ▪ Create up to two (2) Laserfiche templates with up to seven (7) fields each ▪ Create up to two (2) Laserfiche User Groups ▪ Set entry access security for up to two-level ▪ Conduct one (1) session (three (3) hours total) of remote “train the trainer” training on Basic Laserfiche and User functionsdeployment.