Sample Statement of Work for a New ccmMercury Database
Proposed Schedule
| 1 Analysis |
| 2 Detailed Design in Development Environment, including custom reports |
| 3 Pilot Testing |
| 4 Implementation into Production Environment |
| 5 Installation Sign Off and Documentation |
| 6 End User Training / System Administrator Training |
| 7 Post-implementation Support |
| 8 Other optional ccmMercury components |
Project Overview
The goal of this project is to configure a new database within the CLIENT's ccmMercury application to be used for CORRESPONDENCE TRACKING.
The project has been divided into multiple phases, which are described below.
1 - Analysis |
| Team Members |
- WorkDynamics Project Leader
- Client Technical and Business Resources
- Client ccmMercury System Administrator
|
| Description |
- A fit analysis will be conducted to determine the best way to install and configure ccmMercury. Interviews will be held with the business unit to ensure all requirements (reports, templates, pick lists, user roles, etc.) are gathered and verified by the Client.
|
| Deliverables |
- Documentation outlining the proposed ccmMercury functional specification setup will be presented. This will be based on the Project Leader's knowledge of how ccmMercury can be set up for maximum workflow efficiency. This deliverable will include a data design document and an outline of the security / configuration requirements.
|
2 - Detailed Design in Development Environment + custom reports |
| Team Members |
- WorkDynamics Project Leader
- Client Technical and Business Resources
- Client ccmMercury System Administrator
- Client Key Users
|
| Description |
The product design and implementation phase consists of designing/creating the ccmMercury GUI, restriction set and account information based on the analysis phase. The activities consist of:
Development Design:
WorkDynamics will work with the Client to design a system that molds to their business requirements. This will include designing the data-entry screens and associated pick lists; defining and configuring the field tool tips, properties and validations; and determining the user roles and priviledges required and putting them in place.
Creation of custom Templates & Reports:
WorkDynamics will design a few typical RTF Templates such as Routing slip, Notification, Standard letter templates; a few typical RTF Reports such as Summary and Detail listing reports; and if applicable, custom Crystal Reports.
|
| Deliverables |
- A fully-functional ccmMercury Pilot configuration will be made available to users for functional and integration testing.
- Custom reports running within ccmMercury.
|
3 - Pilot Testing |
| Team Members |
- WorkDynamics Project Leader
- Client Key Users
|
| Description |
- Train and assist ccmMercury User(s) and/or CCM Account Managers with any aspect of the functional and integration testing. Make adjustments along the way as necessary.
|
| Deliverables |
- The trained ccmMercury User(s) will test the Pilot database to ensure it meets the business and functional requirements of CLIENT.
|
4 - Implementation into Production Environment |
| Team Members |
- WorkDynamics Project Leader
- Client Technical Resources
- Client ccmMercury System Administrator
|
| Description |
- If required, installation of ccmMercury application on server(s).
- Creation and configuration of database(s), tables, group(s), users, and permissions.
- Installation of the ccmMercury files on user workstations. The creation of the account profiles is included as part of this task.
- If sharing the same ccmMercury database with the existing ccmMercury applications, re-inputting of CCM Account Manager information into the production database for the new setup.
|
| Deliverables |
- A document outlining the ccmMercury installation will be presented. This document will contain technical information on the ccmMercury implementation.
- Users will have access to the ccmMercury modules that they have been permitted to use.
- NOTE: The scheduling of the installations on the users desktop should be coordinated with the training schedule to ensure immediate access to the new ccmMercury database following training.
|
5 - Installation Sign Off and Documentation |
| Team Members |
- WorkDynamics Project Leader
- Client Technical Resources
- Client ccmMercury System Administrator
|
| Description |
- User, system and operations documentation will be provided. The installation document will be specific to your environment and will provide the installation information relating to ccmMercury. Also, the location and necessary rights, account, etc for the database will be outlined.
|
| Deliverables |
- The final documentation will be provided upon completion of the project, and will include the sign-off sheet.
|
6 - End User Training / System Administrator Training |
| Team Members |
- WorkDynamics Project Trainer
- Client Users
- Client ccmMercury System Administrator
|
| Description |
- WorkDynamics will provide a 1-day Introductory Training session for ccmMercury Users and a 2-day Administrator Training session for a designated ccmMercury Administrator, as required.
|
| Deliverables |
- An Introductory training class for each student, resulting in trained users capable of working with the software.
- If required, an administrator training session, resulting in a trained administrator capable of performing ccmMercury Administration duties. It would be preferable if the designated individual have a technical background including supporting software applications.
|
7 - Post-implementation Support |
| Team Members |
- WorkDynamics Project Leader
- Client ccmMercury System Administrator
|
| Description |
- Activities include assisting the Client ccmMercury System Administrator with the maintenance of the ccmMercury software
|
| Deliverables |
- WorkDynamics Technologies' Project Leader is on-site for 1 working day assisting the CCM Administrator with the maintenance of the ccmMercury software installation.
- Support user community as required.
|
8 - Other optional ccmMercury Components |
| Team Members |
- WorkDynamics Project Leader
- Client Technical Resources
- Client ccmMercury System Administrator
|
| Description |
Activities might include setting up one or many of the ccmMercury optional modules, such as:
- Automatic Event-based Notification
- ccmEforms
- Silent DM integration
- ccmMX Exchange
- ccmWorkflow
- Full-Text Searching
- Keyword Searching
- Conversion from previous versions of CCM or other applications
|
| Deliverables |
- As required for each component.
|
Assumptions
All services are in relation to the ccmMercury product. Future product lines are outside the scope of this proposal.
All estimates are based on a 7.5-hour workday.
This statement of work does not provide for the cost of the software, the cost of maintenance or the cost of support services.
Ready access to the key Client staff or other third-party staff is essential for the successful completion of this project.
Client staff or other third-party staff will be prompt in providing approval and information when and as requested by WorkDynamics.
The Client is responsible for the acquisition or identification of all the necessary hardware and/or software. This includes a workstation for the WorkDynamics resource.
The Client is responsible for setting up network rights and DBA services including:
- Installing the Database engine.
- Creating the ccmMercury database (creating the Database and access).
- Running the scripts provided by WorkDynamics to create the tables.
- Creating all necessary user accounts in the DBMS and granting the proper access rights.
