How Can We Help?
Implementation project scopeImplementation project scope
Who is this page for?
This page is intended for clients who have recently bought Pure, or a new part of Pure, and are currently or will soon be working on an implementation project with a Pure Implementation Manager. It provides general information that is applicable to all Pures; your Implementation Manager will help you address the details specific to your individual case.
Introduction
During the preparation phase, your Implementation Manager (IM) will collect information from you to establish and document the scope of your implementation project. This will help you with resourcing and scheduling. When the scope has been documented, you should review it, make any necessary changes together with your IM, and sign it off.
The project scoping document
The project scope should be documented in the Monday.com project board, in a document on the Project Scoping activity. The content of this document will vary depending on the type and complexity of your Pure implementation, but as a minimum there should be sections on:
- System landscape and integrations
- Identification of all system that will be integrated with Pure (e.g. HR data system, Publication repository, SSO, Pure Portal; also online sources such as Scopus, WoS, Scival, Funding Institutional)
- Section for each integration that lists what data it includes and whether the integration is an import or a synchronisation
- Configuration of Pure
- Identification of areas/content types that need special attention during the configuration of Pure (e.g. Research Output types and workflow, Award Management processes)
- Business processes
- Identification of your business processes that will be affected by the Pure implementation (e.g. creation, enrichment and validation of Research Outputs, Award Management processes, Reporting)
- Miscellaneous
- List initial decisions about, e.g., Pure UI and submission languages
If you have special requirements that should be documented in the project scope, feel free to add additional sections and adjust if needed.
Input used to establish the project scope:
- The Pure agreement, including Pure modules and services
- The introductory call, kickoff meeting, workshops and other meetings during the preparation phase
- Pure Tasks and Configuration Decision Log
The project scope will also be used for planning workshops and project meetings, and creating and scheduling the project plan.
Updated at July 27, 2024