How Can We Help?
Identifying your implementation stakeholdersIdentifying your implementation stakeholders
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 will ask you to provide information about the stakeholders for your Pure implementation in a stakeholder register, including their roles and responsibilities in the project. Please see below for a list of required roles.
Your Implementation Manager will also provide you with a list of Elsevier stakeholders for your project, together with their contact details.
Pure implementation stakeholder roles
| Role | Responsibilities | Comments |
| Project Sponsor | Approves budget and resources | The Project Sponsor does not usually need to attend implementation meetings |
| Project Lead | Manages internal progress and resources; maintains records in the project tracking board; acts as the main point of contact with Elsevier's Implementation Manager and with the Project Sponsor | The Project Lead role may be played by the same person as the Pure Administrator role |
| Pure Administrator(s) | Runs Pure after launch | The Pure Administrator role may be played by the same person as the Project Lead role; it is recommended to have 2 to 4 Pure Administrators after launch |
| IT Manager | Completes technical tasks (such as authentication configurations and URL changes); may also take responsibilities for integrations built by developers after launch | The IT Manager may complete technical tasks themselves, or assign them to colleagues who do not necessarily need to be involved in the entire implementation |
| Developer(s) | Builds integrations to synchronise data from the client institution's systems into Pure, or extracts this data and imports it into Pure | Developers need the technical skills to build XML or API integrations between the client institution's systems and Pure |
| Data Owner(s) | Advises developers and other stakeholders on the data stored in the client institution's systems that are to be integrated into Pure (e.g. HR systems, research repositories and finance systems) | At least one data owner is required for each system from which data will be synchronised/imported into Pure |
Updated at March 10, 2025