Statement of Work
Introduction
The purpose of this document is to describe the approach PairSoft and Client will follow to implement a basic implementation of PaperSave with transaction automation to support a gift, i.e., check, capture and ingestion process for a new PaperSave client. The implementation will be done using a prefabricated workflow template that cannot be modified during this implementation. The workflow will be integrated with Client’s Blackbaud Raiser’s Edge (RE) NXT application using Sky API.
In addition, OCR will be configured to accommodate the scanline, as described below. *if included
Scope
Service | Description |
---|---|
PaperSave application software |
|
Configuration of standard workflow and Auto Entry |
|
PaperSave Native OCR |
|
OCR configurations to accommodate scanlines *if included |
|
Auto Entry |
|
Project Overview and Responsibilities
MILESTONE 1: Preparation & Launch | Pairsoft | Client |
---|---|---|
Conduct technical planning meeting
|
✓ | |
Provision PaperSave 7 environment | ✓ | |
Test PaperSave components
|
✓ | ✓ |
Install and test any applicable PaperSave Client components on all other workstations and/or terminal servers
|
✓ | ✓ |
MILESTONE 2: Software Setup | Pairsoft | Client |
---|---|---|
Deploy and test the workflow template | ✓ | |
Prepare and review design document
|
✓ | ✓ |
Setup drop points
|
✓ | ✓ |
MILESTONE 3: Train & Test | Pairsoft | Client |
---|---|---|
Conduct remote trainings (approximately 4 hours)
|
✓ | |
Conduct User Acceptance Testing (UAT)
|
✓ | |
Complete the testing plan and report any defects to PairSoft within 5 business days
|
✓ | |
Provide support to UAT users
|
✓ | |
MILESTONE 4: Go-Live | Pairsoft | Client |
---|---|---|
Remove test items and Go-live | ✓ | ✓ |
Provide hypercare support (for up to 2 weeks)
|
✓ | |
Deliver Project Closure and Support Transition Document
|
✓ | |
Acceptance: If PairSoft does not receive timely written notification within five (5) days of any defects during the UAT, the project shall be deemed accepted. If the application is placed into production and invoices are being processed, the project shall be deemed accepted and will be closed.
Project Governance
Changes
If the parties agree to any changes to this SOW, they shall execute an amendment to this SOW effecting such changes (“SOW Amendment”). No additions or other changes to this SOW shall be effective unless such changes are in writing and signed by both parties in the form of a SOW Amendment.
Out of Scope
Any services and/or activities not listed in the tables above are out of scope and excluded from the Professional Services project.
Assumptions
The client shall provide PairSoft with all information relevant to the services to be performed and shall cooperate and provide PairSoft with all assistance as may be required for PairSoft to perform the services. Client grants PairSoft employees’ access to their data and environment to provide the scoped solutions outlined in the SOW.
Exclusions of PairSoft Responsibility
- Installation and / or configuration of third-party products including but not limited to Microsoft Office and SharePoint
- Hardware procurement or licensing
- Configuration of any hardware components including desktop and multi-function scanners
- Network configuration or troubleshooting, including permissions for file sharing or access
- Support for users across multiple domains
- Development of Client specific documentation such as Client test plans, implementation plans, custom Client training materials, and Client specific system documentation
- Training services other than those specified in this statement of work
- Onsite training (which, will in any case, requires a minimum duration of two business days)
- Weekend work or after-hour deployments are excluded from the delivery methodology