Statement of Work

Prepared for: Error! Unknown document property name.

M-Files Inc.

5050 Quorum Drive, Suite 600

Dallas, TX 75254
TABLE OF CONTENTS

PURPOSE............................................................................................................................................................................. 4
BACKGROUND .................................................................................................................................................................... 4
PROJECT SCOPE .................................................................................................................................................................. 4
IMPLEMENTATION TYPE ................................................................................................................................................. 4
M-FILES CORE PRODUCT ................................................................................................................................................ 4
License Count ................................................................................................................................................................. 4
M-FILES DATABASE ENGINE ........................................................................................................................................... 4
M-FILES Modules ............................................................................................................................................................ 4
[Account] DOCUMENT MIGRATION ............................................................................................................................... 5
PROJECT PHASES ................................................................................................................................................................ 5
PHASE 1: REQUIREMENTS GATHERING AND SOLUTION DESIGN ................................................................................... 5
PHASE 2: SOLUTION DEVELOPMENT and Implementatiion ........................................................................................... 6
PHASE 3: SOLUTION TESTING, Training and Handover .................................................................................................. 6
FUTURE / OUT OF SCOPE ITEMS .................................................................................................................................... 7
PROJECT EXECUTION .......................................................................................................................................................... 8
Project Management Methods and Tools ...................................................................................................................... 8
PROJECT ACTIVITIES, SCHEDULE AND CHECKPOINTS ........................................................................................................ 9
Project Initiation ............................................................................................................................................................. 9
Functional Requirements and Technical Specifications ................................................................................................. 9
Design ........................................................................................................................................................................... 10
M-Files configuration and implementation .................................................................................................................. 10
Migration ...................................................................................................................................................................... 10
Testing (M-Files) ........................................................................................................................................................... 11
Acceptance and Deployment testing ([Account]) ........................................................................................................ 11
Deployment .................................................................................................................................................................. 11
PROJECT MANAGEMENT PROCESSES .............................................................................................................................. 12
ESCALATION PROCESS .................................................................................................................................................. 12
CHANGE MANAGEMENT PROCESS ............................................................................................................................... 12
ISSUE MANAGEMENT PROCESS ................................................................................................................................... 12
COMMUNICATION MANAGEMENT PROCESS .............................................................................................................. 12
RISK MANAGEMENT PROCESS ..................................................................................................................................... 13
PROJECT RESPONSIBILITIES AND DELIVERABLES ............................................................................................................ 14
M-FILES RESPONSIBILITIES AND DELIVERABLES ........................................................................................................... 14
ON-GOING PROJECT MANAGEMENT ....................................................................................................................... 14
STANDARD REVIEW AND COMPLETION CRITERIA ................................................................................................... 14

2
 [Account] RESPONSIBILITIES AND DELIVERABLES ........................................................................................................ 15
ON-GOING PROJECT MANAGEMENT ....................................................................................................................... 15
KEY PROJECT ASSUMPTIONS ........................................................................................................................................... 16
M-FILES ROLE DEFINITIONS .......................................................................................................................................... 16
SIGNATURE PAGE ............................................................................................................................................................. 17

3
PURPOSE
This SOW, when executed by M-Files and [Account], describes the project deliverable(s) and proposed level of effort
that is anticipated in supporting all phases of the M-Files Implementation (herein referred to as "Project"), pending
confirmation of requirements.

The project's deliverable(s) and services are the result of the discussions between M-Files and [Account] that have
taken place prior to the development of this SOW.

This SOW describes most general project components including processes, resources, deliverables, and tasks required
to support the project. The applicable contents of this document will be reviewed during the Project's Kick Off /
Engagement Launch Meeting.

BACKGROUND
[Account] is looking to procure an enterprise Document Management System to capture and store various documents
for the HR department within the company. The initial roll-out of the system will be limited to the Human Resources
department.

Detailed Requirements for [Account] can be found in the “M-Files Scoping Worksheet” document.

PROJECT SCOPE

IMPLEMENTATION TYPE

 On Premise

M-FILES CORE PRODUCT

 M-Files DMS
o M-Files 2015.1 or later

LICENSE COUNT

M-Files license count for this phase of the implementation is

 0 Named
 0 Concurrent
 0 Read Only

M-FILES DATABASE ENGINE

 Microsoft SQL Server 2008R2 or higher to be provided by Customer

 M-Files Firebird embedded database engine

M-FILES MODULES

 M-Files OCR Modules (0)

 Additional Server Licenses (0)
 Reporting Module (0)

4
[ACCOUNT] DOCUMENT MIGRATION

 M-Files will import < description and number of files > into M-Files with initial implementation.
 Location of existing documentation: Shared Windows folders

PROJECT PHASES

PHASE 1: REQUIREMENT S GATHERING AND SOLU TION DESIGN

Task Owner

Planning / Project Management

Assign M-Files Services Team M-Files

Project Oversight M-Files

Discussion of resources and people required for the implementation M-Files / [Account]

Discussion of options available when performing the implementation M-Files / [Account]

Introduction to M-Files M-Files / [Account]

Phase 1, 2 and 3 Sign Off M-Files / [Account]

Requirements Gathering
Detailed needs analysis for the initial implementation M-Files / [Account]

Design
Metadata Structure Definition M-Files / [Account]

Permission / Security / Access Definition M-Files / [Account]

Creation of detailed design document M-Files / [Account]

Phase 1 Assumptions

 [Account] will provide sufficient resources to take part in requirements gathering sessions.
 M-Files and [Account] will sign off on Requirements and Detailed Design Document before Solution
Development begins

5
PHASE 2: SOLUTION DEVELOPMENT AND IMPLEMENTATIION

Task Owner

Implementation

Installation of the M-Files server in the [Account]’s environment M-Files

Design of method for distributing the M-Files Client to user workstations M-Files / [Account]

Design of backup, restore and maintenance procedures M-Files / [Account]

Development / Configuration

Configuration of the M-Files Vault according to [Account]’s requirements M-Files

Creation of up to < > Common Views M-Files

Configuration of Active Directory Integration and User/Group Accounts M-Files

Configuration of Web Access Server, Mobile, and Client

M-Files / [Account]
Note: < a blurb about SSL certificate costs if applicable>

Configuration of Vault and Content security M-Files

Additional Servers

Installation and configuration of Replication to (2) additional servers M-Files

Data Migration

Perform and administer the migration process of HR documentation only M-Files

Phase 2 Assumptions

 [Account] will provide Hardware, Operating Systems, and Databases that meet requirements specified in the
M-Files Technical Data Sheet

PHASE 3: SOLUTION TE STING, TRAINING AND HANDOVER

Task Owner

Testing
Functional testing and validation of the M-Files solution M-Files / [Account]

Assistance with user acceptance testing M-Files / [Account]

Training
Administrator and end user training sessions M-Files / [Account]

Handover
Handover of project materials M-Files / [Account]

Go-Live assistance and support M-Files

6
FUTURE / OUT OF SCOPE ITEMS

There will be no deliverables beyond what is stated in this SOW. Any deliverables that are not included in this
document will need to have an additional SOW generated outlining the scoped deliverables and may require
additional hours. Future projects will also require a separate SOW. Out of scope services include:

 M-Files development of custom features using the M-Files API not specified in this SOW
 Implementing of automatic values or validation for properties not listed in this SOW
 Integrations to legacy systems not listed in this SOW
 Installation or configuration of:
o Workflows
o Reporting
o Templates
o E-Signatures
 Generation of UAT test scripts materials by M-Files
 Configuration of Archiving and retention policies
 Installation or configuration of hardware and operating systems
 Installation or configuration of scanner hardware or scanner drivers

7
PROJECT EXECUTION

Project execution is a qualified and carefully controlled process at M-Files. The following paragraphs outline the M-Files
project management methods, models, tools, and responsibilities. The purpose is to clarify how projects are
professionally managed at M-Files and how also the Enterprise Content Management project with [Account] will be
successfully managed.

PROJECT MANAGEMENT METHODS AND TOOLS

Project deliveries are divided into smaller execution phases which are divided into smaller work packages and tasks.
This is done to easily track and follow project progress and to understand all task dependencies and their relation to
each other's and possible 3rd party dependencies. Time estimates to complete tasks and work packages considers the
complexity, dependencies, and risks. Based on that, work effort estimates are completed for each work package and
execution phase. It must be noted that the estimated efforts in the project plan are initial estimates only and will be
further refined the completion of technical and functional requirements definition.

During the project, the execution phases, work packages, tasks, and resource tracking are managed using Microsoft
Project and various M-Files modules. Requirements are captured in an M-Files Services vault, where the hours to
complete tasks are tracked.

It must be noted that M-Files Enterprise Content Management software is a productized solution, so all tasks performed
during the project are configuration changes, scripts, integrations to [Account]'s IT systems and small application
changes/integrations and not the implementation of totally new software or features to M-Files product, unless
otherwise defined. The project is executed using industry accepted project management principles to ensure
transparency and quick reaction to [Account] needs and possible unpredicted problems.

Since the project uses industry standard methodologies, all defects and findings during the project are internally
reported directly to the assigned system specialists and corrective actions started right away. During the development
and implementation phase, the [Account] reports findings to the M-Files Project Manager and the Project Manager is
responsible for communicating the progress of the findings to the [Account] project manager and team. The M-Files
and [Account] project teams will evaluate the priority and severity of the findings, and collectively decide on the most
appropriate course of action. Defects and issues after go-live and short term post go-live support are reported to the
M-Files [Account] Support organization according to the Support and Maintenance agreement.

8
PROJECT ACTIVITIES, SCHEDULE AND CHECKPOINTS

In the Project Plan, the project is divided into several phases, work packages, and tasks. This enables easier follow-up of
project progress and status for the [Account] and brings more transparency to the project. Phases may depend on each
other and any parallel execution will be collectively agreed to. Some phases may be accepted by the Steering Group
before the previous phase is ready and accepted. Dependencies and acceptance milestones are defined in the project
schedule. The schedule also contains effort and time needed for documentation, planning, execution, testing and M-
Files project management. The [Account]'s effort and time in project group meetings or Steering Groups is not estimated
since the number of people involved is not known.

Delivery phases and a generic overall schedule are described in the appendix and this schedule will be updated and
ready for the first Steering Group meeting. It shall be noted that if the SOW gets delayed, those delays will impact the
delivery schedule. It shall be noted that any dates mentioned are assumed based on a current limited understanding
of the [Account] needs, and will be updated during the completion of contract negotiation. The project schedule will be
specified and agreed with the [Account] before project plan signoff can occur.

The main generic project activities and milestones, which are cross referenced with the [Account] specific phases in the
attached detailed schedule, are as follows:

- Project Initiation

- Functional Requirements and Technical Specifications Completed

- System Design Completed

- System Implementation Completed

- Migration Completed

- M-Files Testing Completed

- Acceptance Testing Completed ([Account])

- Documentation Completed

- Training Completed

- Go-live Support

PROJECT INITIATION

The project starts when the SOW with the [Account] is approved and signed on both sides. The [Account] and M-Files
establish project teams and the Steering Group to manage the project and the first Steering Group meeting. The M-Files
project manager, the solution architect and system specialist, as well as other project members will be nominated
before the project starts. Once the members are named, the project plan is updated and will be presented in the first
Steering Group with the [Account]. In the first Steering Group all members of the project groups and Steering Group
should be named on both sides.

The outcome of the phase is a delivery agreement and the first approved version of the project plan. These documents
are prerequisite for further project phases.

FUNCTIONAL REQUIREME NTS AND TECHNICAL SPECIFICATIONS

During this phase, detailed functional and technical requirements are agreed with the [Account]. All requirements for
the entire project, all phases, should be detailed during this period, as it serves as the input for the complete solution
design.

It may happen that the detailed functional and technical requirements turn out to be significantly different to the
original assumptions used to estimate the work efforts in the proposed solution, and in that case both M-Files and the

9
[Account] need to revise the technical and functional requirements or manage the differences through the change
control process. In this phase also replication needs are agreed with the [Account] and initial testing plans are generated
to cover all site deployments. During this phase, all migration needs must be identified and detailed, including available
interfaces to existing systems, quantity, database structure and the data model. The expected outcome is the migration
process, and how the data to be migrated maps to the M-Files metadata structures.

During the phase, the project documentation, as defined in the Requirements Specification and Planning phase is stored
in the project bank and is available to the [Account]. Functional and Technical requirements must be approved in
Steering Group before phase acceptance.

The phase cannot be started before Project Initiation is completed.

DESIGN

The purpose of the design phase is to translate the functional requirements and technical specifications into a solution
architecture. The overall system design will be completed and approved during this activity.

The overall architecture may include items like:

- Solution topology

- Object model

- Metadata structure

- Workflow definition and structure

- Dependencies, commonalities and cross-referencing

- Security and permissions matrix

- Design for methods and connections for integrating to outside data sources and 3 rd party applications

During this phase M-Files installs the M-Files server and vaults to the development, testing and QA environments
provided by either M-Files or the [Account] so that metadata, workflow, permissions and other software specific design
activities may commence.

M-FILES CONFIGURATION AND IMPLEMENTATION

During this activity M-Files is configured to correspond to the agreed requirements in. The configuration of agreed
metadata structures, workflows and scripts as well as views and other M-Files functionalities are completed at this time,
for the specific phase. Reporting is also configured during the phase. It shall be noted that amount of workflows and
granularity of metadata structures is not known so the current estimations include an assumed quantity of generic
scripts and workflows. The phase also contains archiving with normal archiving rules. The estimated hours also contains
time for [Account] specific M-Files features. At this point it is not clear what the specific features are, and consequently
the development effort is also an estimate.

The solution, that includes the configuration, development and any other pre-production activities will be completed in
the development environment, and moved to a testing and QA environment for the [Account] to complete evaluation,
testing quality assurance and acceptance before moving the solution to the production environment. It is assumed that
connections to any external databases, data sources, and 3 rd party software will be made available by the [Account]
during development, testing and QA activities.

MIGRATION

Migration from existing systems and data sources is completed to M-Files during this activity. The details surrounding
interfaces to exiting databases, current data format, the expected metadata structures and how data can be exported
from the existing systems are not clearly defined at this stage, so migration estimates are provided with generic
assumptions.

10
It is assumed that the [Account] will take responsibility for cleaning up of existing data (removing duplicates, unwanted
documents etc.) and depositing the data in a staging environment prior to migration. Migration is normally time-
consuming and includes time to configure and run migration tools if database connections or exports to a staging
environment is available. In some cases migration may be done manually, e.g. add some metadata if the source does
not have metadata included. This should typically be done by the [Account] and supported by M-Files.

Migration can be started after the M-Files data structures are in place from the previous activity, and the interfaces with
existing systems are in place.

TESTING (M-FILES)

During testing, the M-Files configuration, migrations and implementation are tested according to the test plans created
in the requirements and specifications activities. Efforts required in testing depends on the amount of customization in
each solution entity. The phase cannot be started before implementation and migration is complete and accepted. The
schedule and effort estimates include the assumption that multiple locations have similar configurations as the main
site. Testing is then more focused on replication, user accesses, configuration copies, and all installation and integrations
are working as expected.

It is also suggested that a pilot or limited release of the solution is run during this part, and feedback gathered to a
central location in the Project Bank. The feedback will then be analyzed and improvements implemented before
production. The process and improvements will be agreed with the [Account] and some changes may result in change
requests and change orders.

ACCEPTANCE AND DEPLOYMENT TESTING ([ACCOUNT])

The [Account] will execute their acceptance and deployment testing during each phase, initially in the test and QA
environment, and subsequently in the production environment. Test cases and testing are performed by the [Account]
and M-Files will support as needed. The [Account] will follow the agreed defect process if issues are found and M-Files
will implement the needed fixes according to commonly agreed priorities. The [Account] will have scheduled time to
complete testing and test approval will be given to M-Files in written form. Testing details need to be agreed with the
[Account] since it is dependent on available resources from the [Account]. M-Files has existing and current processes
for acceptance and deployment testing to ensure quality and effectiveness of the delivery. These processes will be
detailed in the first version of the project plan prior to the start of the project. Acceptance and deployment testing
cannot be started before M-Files testing is completed.

Testing for each phase is completed after written approval is received from the [Account]. The Steering Group confirms
the approval.

DEPLOYMENT

M-Files is deployed for production and taken into use at all locations that are relevant to the specific phase. M-Files
provides enhanced go-live support during this activity. All previous phases must be approved before this phase can be
approved. The [Account] approves the phase in written form.

11
PROJECT MANAGEMENT PROCESSES

ESCALATION PROCESS

The M- Files’ and [Account] Project Managers will discuss and agree to an Escalation Process to address any high
priority issues that arise during the Project.

CHANGE MANAGEMENT PROCESS

The M-Files’ Change Management Process is the method by which changes to the Project (e.g. to the scope,
deliverables, timescales or resources) are formally defined, evaluated and approved prior to implementation. The
purpose of our document is to provide a formal process for managing change control. The process entails completing
control procedures to ensure that, if implemented, the change will cause minimal impact to the objectives of the
Project.

The Change Management Process is used to ensure that every change identified is formally:

 Communicated
 Documented
 Reviewed
 Approved
 Implemented
 Budget Accounted for

ISSUE MANAGEMENT PRO CESS

The M-Files’ Issue Management Process allows issues which are currently affecting the ability of a Project to produce
the required deliverables to be formally managed. The process entails completing a variety of review techniques to
assess the level of impact that the issue is having on the Project and then undertaking a range of actions to resolve or
reduce the issue as appropriate.

The Issue Management Process is used to ensure that every issue identified is formally:

 Communicated
 Documented
 Monitored
 Reviewed
 Resolved

COMMUNICATION MANAGE MENT PROCESS

The M-Files’ Communication Management Process involves identifying the information and communication needs of
the stakeholders. Our Plan establishes expectations of proactive communication between team members and
documents what the team agrees to do. This includes determining what needs to be communicated, what team
meetings will be held, when the information should be distributed, how the information will be delivered, and how
frequently.

A Communication Plan is developed by the Project team early in the Project to define the:

12
  Project stakeholders and other target audiences
 Message/objective/approach for each stakeholder or audience
 Schedule of regular meetings
 Format, method, frequency, due date and publish date of each communication
 Individual responsible for creating and delivering each communication

RISK MANAGEMENT PROC ESS

The M-Files’ Risk Management Process includes a Project Risk evaluation and steps to be taken to identify, document,
track and plan preventive measures in order to keep risks from occurring, as well as reduce the impact of risks should
they occur. This process is to be initiated in the Planning Phase as well as all other Phases of the Project.

Risk Planning includes:

 A list of all of the foreseeable risks that may arise during the Project
 A rating of the likelihood of occurrence
 A rating of the impact if the risks occur
 A set of preventative actions to reduce the likelihood
 A set of contingent actions to reduce the impact if the risk triggers
 A process for managing risks through the Project
 A notification of the risks to stakeholders

The output of the risk planning at the Project initiating phase will be documented in the Risk Log. Risks identified
throughout the Project will also be tracked and updated in the Risk Log.

13
PROJECT RESPONSIBILITIES AND DELIVERABLES

M-FILES RESPONSIBILI TIES AND DELIVERABLE S

ON-GOING PROJECT MAN AGEMENT

M-Files will provide on-going Project Management for the M-Files responsibilities in this SOW. The purpose of this
activity is to provide direction to the M-Files Project personnel where agreed and to provide a framework for Project
planning, communications, reporting, and procedural and contractual activity. This responsibility includes the
following tasks:

 Managing and coordinating the day-to-day activities of the Project for M-Files resources assigned to the
Project where agreed.
 Develop the Project Plan for M-Files deliverable(s) and services.
 Managing change control, time reporting, status reporting and issue resolution throughout the Project
related to M-Files deliverable(s) and services.
 Implement processes in coordination and agreement with [Account] for monitoring and control of the
Project.
 Assign appropriately skilled M-Files Project Consulting personnel to the relevant tasks in the project plan.
 Creating and maintaining Project Documentation for M-Files deliverable(s) and services.
 On-going adherence to the SOW and the contractual responsibilities of both M-Files and [Account] with their
Project Manager.
 Maintain acceptable Project communications in cooperation with the [Account] Project Manager.
 Establish documentation and procedural standards for deliverable materials.
 Prepare and maintain a project plan which lists the activities, tasks, assignments, milestones and estimates
included in the SOW.
 On-going review Project tasks, schedules, and resources and adjusts as appropriate.
 Measure and evaluate progress against the plan and report that information.
 Review the invoice and billing procedures to be used on the Project with the [Account] Project Manager.
 Work with the [Account] Project Manager to address and resolve deviations from the baseline project plan.
 Conduct regularly scheduled Project Status Meetings, where agreed with [Account].
 Prepare and submit status reports to the [Account] Project Manager within an agreed upon timeframe.
 Administer the Project Change Control Procedures in cooperation with [Account] Project Manager where
required.
 Provide [Account] Project Manager with information to incorporate into the overall project plan.

STANDARD REVIEW AND COMPLETION CRITERIA

Each M-Files deliverable as defined above will be completed and reviewed in accordance with the following
procedures:

 One soft copy draft of the deliverable material will be submitted to [Account]'s Project Manager. It is the
[Account] Project Manager's responsibility to make and distribute additional copies to any other reviewers.
 Within five (5) business days of receipt, the [Account] Project Manager will provide the M-Files Project
Manager with the agreed upon completion, which can be soft copy or hard copy or provide the M-Files
Project Manager with a written list of requested revisions. If M-Files receives no response from the [Account]
Project Manager within five (5) business days, then the deliverable material will be deemed accepted.
 In cases where [Account] requires more than five (5) business days for review and acceptance, this will be
agreed between the M-Files and [Account] Project Managers and may result in additional costs which will be
managed under change control procedures.

14
  The M-Files and [Account] Project Managers will mutually agree to a resolution in connection with issues
raised by the [Account]'s timely request for revision, if any.
 Those [Account]'s revisions agreed to by both parties will be made and the deliverable material will be
resubmitted to [Account]'s Project Manager, at which time the deliverable material will be deemed accepted.
 Those [Account]'s revisions determined by both parties to be outside the scope of this SOW will be managed
in accordance with the "Change Management Process" section of this document.
 Any conflict arising from these deliverable materials Completion Procedure will be addressed in accordance
with the "Escalation Process" section of this document.
 M-Files will request [Account] to provide the Software Installation Completion in writing at the agreed upon
timeframe within the License Agreement.

[ACCOUNT] RESPONSIBILITIES AND DELIVERABLES

The successful completion of the proposed scope of work depends on the full commitment and participation of the
[Account] management and personnel. The responsibilities listed in this section are in addition to those
responsibilities specified in the associated Service Agreement and are to be provided at no charge to M-Files.
[Account] is required to perform its obligations in the Service Agreement and SOW without exception. M-Files'
performance is predicated upon the following responsibilities being managed and fulfilled by [Account], as scheduled
in the Overall Project Plan. Delays in performance of these responsibilities may result in additional cost and/or delay
of the completion of the Project, and will be handled in accordance with the "Change Management Process" of this
document.

ON-GOING PROJECT MAN AGEMENT

[Account] must designate a suitable resource to be the [Account] Project Manager for the Project who will:

 Manage and coordinate the day-to-day activities of the Project for M-Files and [Account] resources assigned
to the Project.
 Act as the focal point and liaison for all Project related communication.
 Manage personnel and responsibilities for the Project.
 Serve as the interface between M-Files and the [Account] departments participating in the Project.
 Work with the M-Files Project Manager to administer change control.
 Participate in Project Status Meetings.
 Provide information, data and decisions within the agreed upon amount of working days for each item.
 Help resolve Project issues and [Account] deviations from the estimated schedule.
 Escalate issues within the [Account] environment as needed.
 Review with the M-Files Project Manager any [Account] invoice or billing requirements.
 Manage the overall Project Plan that will have M-Files information incorporated into it.
 Manage and direct the M-Files Technical Consultant during Testing (excluding IVP testing) and roll out.
 The [Account] Project Manager is responsible for scheduling and facilitating any necessary workshops to
ensure that all organizational areas impacted at [Account] are included. Throughout the Project, the
[Account] Project Manager must provide coordination of their organizational resources and third party
vendors to effect timely and efficient utilization.
 In addition to the [Account] Project Manager, appropriate members of the [Account] management and
executive staff are required to participate in the Management Status Review Meetings to provide appropriate
oversight and direction.

[Account] acknowledges that M-Files' ability to perform Professional Services under this SOW is dependent upon
its cooperation and timely procurement, supply and management of the required third party resources. To the
extent [Account] fails to cooperate or provide third party resources, any delay or inability to perform by M-Files

15
 shall be excused. [Account]'s obligation to pay for Professional Services hereunder shall not be excused, and
[Account] shall pay the Fee invoiced for the Project. In addition, if [Account] fails to cooperate or provide third
party resources results in M-Files incurring additional expenses, [Account] shall promptly reimburse M-Files for
such additional expenses so incurred.

KEY PROJECT ASSUMPTIONS

 The executed Statement of Work and the related signed Order Schedule are required for project work to
begin. Project work will begin at the earliest availability in which M-Files and [Account] resources are
available and dates agreed upon.
 [Account] is responsible for hardware, operating system, and database installation and maintenance.
 [Account] will provide on-site or remote access to the environment during the implementation period.
 M-Files ability to deliver Project to [Account] is dependent upon active involvement and access to required
[Account] resources as may be required during the engagement.
 M-Files will provide resources as stated in the Project Organization section for the Project. Other M-Files
resources may be involved as mutually agreed by [Account] for specific expertise and [Account] understands
these services will be invoiced at the applicable rate per the M-Files Professional Services Price List.
 M-Files resources are to be scheduled on a basis of an 8-hour day between the hours of 8am to 5pm Central
Standard Time, Monday to Friday, except public holidays -- regular business hours and can be adjusted
[Account] ‘s work schedule. Time zone information will be specified by [Account].
 M-Files Project work will occur at an M-Files office location or on-site at [Account] (Note: [Account] is
responsible for all travel and expenses incurred by M-Files Project Team for all work outside of M-Files
location).
 There are no deliverables beyond what is stated in this Statement of Work. Acceptance and release of
deliverables stated in this Statement of Work shall be assumed after five (5) days after deliver and
completion of the deliverables unless [Account] provides written notice of issues to M-Files during the
timeframe.
 The [Account]'s system must comply with the M-Files Technical Data Sheet.
 Any deliverables not within this Statement of Work will be considered out-of-scope and may require
additional hours.

M-FILES ROLE DEFINITIONS

Project Role High-Level Responsibility

Project Manager Work closely with [Account]'s project manager (or PM team) with all aspects of project
planning activities, status reporting, tracking, and communication and provide
coordination of Company resources and ensure alignment between the teams.

Senior Technical Lead Plan and organize the resources related to the project, provide technical subject matter
expertise.

Technical Consultant Develop and implement the configuration changes to the system, assist in development
of training and testing. Work with the [Account] team to ensure smooth integrations.

16
 Solution Architect System architecture and design of overall M-Files implementation in the [Account]’s
environment.

SIGNATURE PAGE

M-Files and Licensee have caused this Statement of Work to be executed by their duly authorized representatives as
of the date first set forth below.

M-Files : Licensee :

M-Files, Inc. [Account]

By : By :

Name : Name :

Title : Title :

Date : Date :

17